Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37772

Support Core: Initializer(after = InitMilestone.COMPLETED) kills Jenkins initialization FSM

      It causes JENKINS-37759 due to the "chicken and egg" problem in Jenkins dependencies. It is an unreleased regression introduced by https://github.com/jenkinsci/support-core-plugin/commit/b252db314f5fb5500a2ea06da20c96137c52badc

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

          [JENKINS-37772] Support Core: Initializer(after = InitMilestone.COMPLETED) kills Jenkins initialization FSM

          Oleg Nenashev added a comment -

          Oleg Nenashev added a comment - https://github.com/jenkinsci/support-core-plugin/pull/73

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          src/main/java/com/cloudbees/jenkins/support/SupportPlugin.java
          http://jenkins-ci.org/commit/support-core-plugin/571a06f6fd4fe744349177e603ae2d7056f680c1
          Log:
          JENKINS-37772 - Get rid of Initializer(after = InitMilestone.COMPLETED) (#73)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/support/SupportPlugin.java http://jenkins-ci.org/commit/support-core-plugin/571a06f6fd4fe744349177e603ae2d7056f680c1 Log: JENKINS-37772 - Get rid of Initializer(after = InitMilestone.COMPLETED) (#73)

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: