Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment error running git reset --hard #20

Closed
bravo-kernel opened this issue Mar 30, 2018 · 1 comment
Closed

Deployment error running git reset --hard #20

bravo-kernel opened this issue Mar 30, 2018 · 1 comment

Comments

@bravo-kernel
Copy link
Contributor

Running into the following when trying to deploy using ember deploy production:

Deploying [===>----] 50% [plugin: git -> prepare]Error: git reset --hard exited with nonzero status

 at ChildProcess.<anonymous> (/home/vagrant/projects/cell-deploy/node_modules/ember-cli-deploy-git/lib/run.js:19:19)

Error: git reset --hard exited with nonzero status
  at emitTwo (events.js:126:13)
  at ChildProcess.emit (events.js:214:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
Pipeline aborted
@bravo-kernel
Copy link
Contributor Author

Solution:

unless you’ve configured it differently, you should have a folder called deploy-<project-name> as a sibling to your <project-name> directory that you’re running ember deploy in

Delete that sibling directory and re-run.

bravo-kernel added a commit to bravo-kernel/ember-cli-deploy-git that referenced this issue Mar 30, 2018
Adds a log message showing the location of the directory where the actual git prepare is running (but only if `--verbose` is passed).

Might be useful for other users encountering git errors and not being able to reproduce/fix because they are not aware of the "sibling directory" being used. Like was the case here ef4#20.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant