|
||||||||||||||
|
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.
Looks like Run.execute always acquired a lock on an older build via LogRotator and Run.delete. And using the Change Log History plugin means that when deleting an older build Jenkins also acquires a lock on a newer build, which is a bug in that plugin. And the change in 1.556 means that Run.delete could also (via dropLinks) acquire locks on both older and newer builds, which in combination with the bug in CLH means that deadlocks are possible.