My point was to clarify the specific case of GlobalConfiguration. I'm not
pretending any Initializer should be after JOB_LOADED.
The deadlock was sneaky, because it can only be reproduced if you have
previous config data. So we haven't spotted it during our tests (because we
start from a clean env) and we ended up releasing something broken.
Julien Henry | SonarSource
2018-04-10 11:59 GMT+02:00 Daniel Beck <m...@beckweb.net>:
> > On 10. Apr 2018, at 11:51, Julien HENRY <julien.he...@sonarsource.com>
> > If you look at the stacktraces, the deadlock occurs in the constructor
> of the GlobalConfiguration, because it ends up calling OldDataMonitor that
> itself access ExtensionList, and that seems to conflict with other plugins
> like GitSCM that also access ExtensionList from its Initializer.
> Right, so in this case it depends on the class you extend. More
> convoluted, but still doesn't look like it can never be earlier than
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> To unsubscribe from this group and all its topics, send an email to
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.