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

exitcode is always 1? #11

Closed
zheli opened this issue Jan 13, 2017 · 4 comments
Closed

exitcode is always 1? #11

zheli opened this issue Jan 13, 2017 · 4 comments
Assignees
Labels

Comments

@zheli
Copy link

zheli commented Jan 13, 2017

It seems the exitcode is always 1? In that case it would hard to tell when the command succeeds/fails..

@zheli zheli closed this as completed Jan 13, 2017
@zheli zheli reopened this Jan 13, 2017
@zheli
Copy link
Author

zheli commented Jan 13, 2017

I got the exitcode by type in "echo $?" after a successful deploy.

@frankV
Copy link
Member

frankV commented Jan 14, 2017

we'll look into it

@jtrotsky
Copy link

This also messes up CI pipeline, as it throws error even when it is SUCCESS.
screenshot 2017-02-26 12 44 50

@frankV frankV added the bug label Feb 27, 2017
@frankV
Copy link
Member

frankV commented Feb 27, 2017

Alright, we're gonna triage this later in the week. Sorry guys - should be an easy fix. If anyone want's to issue a PR it might speed things up.

@frankV frankV closed this as completed in c7c9263 May 28, 2017
frankV pushed a commit that referenced this issue May 28, 2017
closes #11, dev reqs file is updated, fixed some code styling and added a setup.cfg

oopsies

closes #11, dev reqs file is updated, fixed some code styling and added a setup.cfg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants