-
New Feature
-
Resolution: Done
-
Critical
-
-
jenkins-2.220
In Jenkins Configuration-as-Code Plugin the initialization may happen in parallel with Job loading. It may cause various race conditions in the plugin, see https://github.com/jenkinsci/configuration-as-code-plugin/issues/280 for more details.
In order to address this case, I propose to create a new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED. It would allow some plugins to handle extension-based functionality, e.g. to do some Jenkins preconfiguration BEFORE it starts loading jobs.
I would call it "PRECONFIGURATION_COMPLETED" or so.
- is related to
-
JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
-
- Resolved
-
- links to
[JENKINS-51856] Job loading and JCasC conflicts: Introduce new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED
Labels | New: jcasc-compatibility |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |
Summary | Original: Introduce new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED | New: Job loading and JCasC conflicts: Introduce new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED |
Remote Link | New: This issue links to "configuration-as-code-plugin/issues/280 (Web Link)" [ 23021 ] |
Component/s | New: configuration-as-code-plugin [ 23170 ] |
Assignee | New: Francisco Fernández [ fcojfernandez ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Released As | New: jenkins-2.220 | |
Resolution | New: Done [ 10000 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |