Repository navigation
[JENKINS-61694] Groovy Hooks may run before or after JOB_CONFIG_ADAPTED #11440
Description
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 ab12f71 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
Originally reported by 
oleg_nenashev, imported from: Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
- assignee: oleg_nenashev
- status: Resolved
- priority: Major
- component(s): core
- label(s): 2.222.2-rejected, 2.222.4-fixed, jcasc-compatibility
- resolution: Fixed
- resolved: 2020-04-06T09:44:08+00:00
- votes: 0
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
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 ab12f71 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
Activity
jenkins-infra-bot commentedon Mar 26, 2020
Raw content of original comment:
#4606
jenkins-infra-bot commentedon Apr 21, 2020
Raw content of original comment:
Would this address
JENKINS-61694?jenkins-infra-bot commentedon Nov 24, 2025
[Original
relates_tofrom Jira: JENKINS-51856]