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

Groovy Hooks may run before or after JOB_CONFIG_ADAPTED

    • Jenkins 2.230

      After introduction a new milestones in the core,  Groovy hooks may run before or after JOB_CONFIG_ADAPTED depending on how graph is executed. We need to apply a fix in the Jenkins core to ensure that JCasC and Groovy Hooks still interact in a predictable way.

      Proposal:

          [JENKINS-61694] Groovy Hooks may run before or after JOB_CONFIG_ADAPTED

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Labels New: jcasc-compatibility
          Oleg Nenashev made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-51856 [ JENKINS-51856 ]
          Oleg Nenashev made changes -
          Summary Original: Groovy Hooks will not reliably work with JCasC New: Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
          Oleg Nenashev made changes -
          Description Original: After introduction a new milestones in the core,  JCasC and Groovy hooks will not be aligned properly after [https://github.com/jenkinsci/configuration-as-code-plugin/pull/1262] . We need to apply a fix in the Jenkins core to ensure that JCasC and Groovy Hooks still interact in a predictable way.

          Proposal:
           * Revert [https://github.com/jenkinsci/jenkins/commit/ab12f71a48901ab3b78521382057a03e166fe668] to the orifginal state so that init hook behaves as before: after all initialization steps
           * Document Groovy Hooks and explicitly document the state
           * Consider introducing new hooks for specific items like post-job-initialization
          New: After introduction a new milestones in the core,  Groovy hooks may run before or after JOB_CONFIG_ADAPTED depending on how graph is executed. We need to apply a fix in the Jenkins core to ensure that JCasC and Groovy Hooks still interact in a predictable way.

          Proposal:
           * Revert [https://github.com/jenkinsci/jenkins/commit/ab12f71a48901ab3b78521382057a03e166fe668] to the orifginal state so that init hook behaves as before: after all initialization steps
           * Document Groovy Hooks and explicitly document the state
           * Consider introducing new hooks for specific items like post-job-initialization
          Oleg Nenashev made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]

          Oleg Nenashev added a comment -

          Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/4606
          Oleg Nenashev made changes -
          Labels Original: jcasc-compatibility New: jcasc-compatibility lts-candidate

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

              Created:
              Updated:
              Resolved: