Skip codedeploy if build was not mark as success #71
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
Before we run codedeploy if build was not mark as failure. This meant that we deployed for ABORTED, NOT_BUILT and UNSTABLE states as well (http://javadoc.jenkins-ci.org/hudson/model/Result.html) Until there is a finer grained configuration option, it's safer to deploy for SUCCESS builds only. Fixes awslabs#61
|
I would like to merge this in. Can I just check that you've at least done some testing to confirm the new change works correctly? Thanks, |
|
Hey Assaf |
|
Are there any plans to merge this branch. This seems like quite dangerous behaviour for a CI tool |
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.
Before we run codedeploy if build was not mark as failure.
This meant that we deployed for ABORTED, NOT_BUILT and UNSTABLE states as well
(http://javadoc.jenkins-ci.org/hudson/model/Result.html)
Until there is a finer grained configuration option, it's safer to deploy for
SUCCESS builds only.
Fixes #61