The deadlock seems to occurs whatever is in the method annotated by
@Initializer. We tried to put a log at the very beginning of the method and
it was never called.
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.
Julien Henry | SonarSource
2018-04-10 11:35 GMT+02:00 Daniel Beck <m...@beckweb.net>:
> > On 10. Apr 2018, at 10:39, Julien HENRY <julien.he...@sonarsource.com>
> > Could it be possible to improve the situation, by at least completing
> the Javadoc, or maybe detecting and failing fast when a GlobalConfiguration
> tries to use an Initializer earlier than JOB_LOADED ?
> It probably depends on what your initializer does.
> I understand the Javadoc to mean that it needs to be PLUGINS_PREPARED _or
> later_ -- if that (or something similar) would have helped, just file a PR
> to core. Thanks!
> 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.