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.
|Field||Original Value||New Value|
|Priority||Minor [ 4 ]||Critical [ 2 ]|
|Summary||Introduce new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED||Job loading and JCasC conflicts: Introduce new Milestone between EXTENSIONS_AUGMENTED and JOBS_LOADED|
|Remote Link||This issue links to "configuration-as-code-plugin/issues/280 (Web Link)" [ 23021 ]|
|Component/s||configuration-as-code-plugin [ 23170 ]|
|Assignee||Francisco Fernández [ fcojfernandez ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Done [ 10000 ]|