|
||||||||
|
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/d/optout.
In our case, when people check sticky it means that they will fix the problem that they caused, usually compilation problems caused by their code.
While it may means many things, an unstable build doesn't mean the same thing as a failed build. It is usually not the same people that fixes the code that is commited for a project than those who configure Jenkins and make sure there are no unstable builds.
Also, if a build is unstable then fails and is claimed, it is not the responsability of the user who broke the build to repair previous issues.
Just my opinion and I see it is not shared, I might do a pull request for a config change if I find the time.
Thanks for your answer.