JENKINS-68729 Abort the build on error #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, when there were errors (either reported by a build, or a non-zero return code), the build was marked as failed, but continued to the next step. Now, such errors will cause the build to be aborted. A new "Continue On Error" option has been added to provide the old behaviour. However, it was _not_ made the default; this may break compatibility with any existing builds that rely on the old behaviour.
Zastai
changed the title
Zastai
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JENKINS-68729
Previously, when there were errors (either reported by a build, or a non-zero return code), the build was marked as failed, but continued to the next step.
Now, such errors will cause the build to be aborted.
A new "Continue On Error" option has been added to provide the old behaviour. However, it was not made the default; this may break compatibility with any existing builds that rely on the old behaviour.