[JENKINS-37780] Extreme Notification Plugin: Initializer(after = InitMilestone.COMPLETED) kills Jenkins initialization FSM - Jenkins Jira

Type: Bug
Resolution: Fixed
Priority: Blocker
Component/s: extreme-notification-plugin
Labels:
None

Similar Issues:
Powered by SuggestiMate

Show

It causes ~~JENKINS-37759~~ due to the "chicken and egg" problem in Jenkins dependencies, it's caused by https://github.com/jenkinsci/extreme-notification-plugin/blob/0249acced3d5483841e06849a4481c47a7e28fe5/src/main/java/org/jenkinsci/plugins/extremenotification/ServerStateListener.java#L51

See https://github.com/jenkinsci/jenkins/pull/2524#issuecomment-243207783 for the detailed clarification

is related to

JENKINS-37759 Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic

Resolved

links to

CloudBees Internal OSS-1387

Assignee:: Oleg Nenashev

Reporter:: Oleg Nenashev

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2016-08-29 18:50

Updated:: 2017-12-05 05:46

Resolved:: 2016-08-30 22:12