Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: core
-
Labels:None
-
Environment:jenkins-2.7.3-rc
-
Similar Issues:
Description
It is a follow-up task to the investigation of JENKINS-37759. The original theory in this bug was incorrect, and lead to the pull request, which streamlines dependencies between startup tasks. Actually it is not required since Jenkins forces InitMilestone order by InitMilestone#ordering(). But it still makes sense to integrate the PR.
Original PR: https://github.com/jenkinsci/jenkins/pull/2524
Attachments
Issue Links
- is related to
-
JENKINS-37759 Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic
-
- Resolved
-
Oleg Nenashev It's not clear what this issue is about, and why it's an lts-candidate. Could you explain?