|
||||||||
|
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.
@rsandell as noted in the PR comments, while expanding the calls made to Trigger.stop from core might fix the bug as produced by Reload Configuration from Disk, other problematic cases will likely remain—folder moves, etc.—and you will be tracking them all down for a long time. The root problem is that GerritTrigger and related classes hold references to AbstractProject yet are used in global static state, which is inherently risky and a design problem: items are intended by held only from their ItemGroup (ultimately via the Jenkins singleton). I believe my PR corrects that problem, or at least gives the general idea, but the plugin tests would need extensive edits to keep up.