|
||||||||
|
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.
if "UNSTABLE status in general can be "stable" with warnings" then your job is just misconfigured. if "warnings" aren't relevant they shouldn't break the build. I don't consider an UNSTABLE build to be production-ready, so should not be tagged and go further in the build-pipeline