-
Notifications
You must be signed in to change notification settings - Fork 90
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
Prevent silent fail #104
Comments
Hi,
On which version occurred this issue? |
Hi! Thank you for the quick reply! We are using I read the release notes of version So it has been fixed in the new release? |
Hi, so from the above message, in my test exit code wasn't 0 in case of failure:
Exiting with non-zero code is already implemented, may be an issue with code which call |
Hi! Weird, I believe the commands in pipeline steps get wrapped in We are using it as a step alone so it is executed like this:
But everything works fine with other commands/steps! What makes things weirder, I just tried to reproduce the issue and this time it exited with a non-zero code! |
Hi!,
We are using this command in our CI/CD pipeline:
Yesterday this command fails because of a GitHub authorization error, however, it only logs the error instead of exiting with non-zero code this causes the pipeline to continue then exist on another step that depends on what has been downloaded by
fetch
.Please we need an option to exit on error.
The text was updated successfully, but these errors were encountered: