|
||||||||
|
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/d/optout.
50/50
I don't develop such jobs, but other users on my installations usually create such stuff (it's explicitly discouraged by internal usage policies). I can imagine they need the "lastSuccessfulBuild" link in their flows (e.g. for file-system monitors), but I have not seen the real trouble before.
In my opinion, it does not make sense to hide the issue from logs if the issue appears.
BTW, the fix may decrease the master's perfomance due to additional locks, hence I'm not sure about the fix feasibility.