|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I took a look at this. If you're using Maven (as I am), then Maven will call the build UNSTABLE before the TestNG plugin is invoked. If we try to set the build back to successful after this happens, we cannot. This is by design in Jenkins. The build can only go from successful->unstable->failed and not in the other direction, as far as I can tell.
We can still add a field in the plugin that fails the build if the pass/fail ratio dips below a certain percentage, but there are some cases where we can't go back to the success state if it has already been set to something worse than success.
Does anyone have any thoughts on this? I can continue with the pull request, but I don't want to move forward if I'm going to wind up discarding it because this isn't the ideal behavior.