-
Improvement
-
Resolution: Fixed
-
Major
It's a follow-up to JENKINS-37759. Diagnostics should be improved. I consider it is a bug due to the significant impact. We may need backporting to 2.19.x
- is related to
-
JENKINS-37759 Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic
-
- Resolved
-
Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/main/java/jenkins/diagnostics/CompletedInitializationMonitor.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/resources/jenkins/diagnostics/CompletedInitializationMonitor/message.jelly
core/src/main/resources/jenkins/diagnostics/CompletedInitializationMonitor/message.properties
http://jenkins-ci.org/commit/jenkins/0f45609fb20248a227fc1071725d2afa6d1f61af
Log:
JENKINS-37874- Print warnings if Jenkins startup/reload do not reach the COMPLETED state (#2530)JENKINS-37874- Log SEVERE messages if Jenkins does not reach COMPLETED stage during startup or reloadJENKINS-37874- Add Administrative monitor for the COMPLETED stateJENKINS-37874- Polish log messages