Skip to content

Conversation

@tomyam1
Copy link

@tomyam1 tomyam1 commented May 20, 2017

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

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
@asaf-erlich
Copy link
Contributor

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,
-Asaf

@tomyam1
Copy link
Author

tomyam1 commented Jul 7, 2017

Hey Assaf
Sorry. I've not actually tested it.

@Jmcfar Jmcfar self-assigned this Dec 19, 2017
@drmclean
Copy link

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants