|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I am not really sold on this feature. It's not right to mark a build as successful based on a percentage as it could mislead the user. E.g. If the threshold is set at 95% and if 96% tests pass, the build would be marked success, but the failing 4% tests could be the most important tests of the regression.
Do you have a concrete use case in mind? What is the issue with a build being marked unstable? IMO, implementing JENKINS-9838, in some ways similar to how Emma Coverage Report plugin works would be better.