Status: Closed (View Workflow)
Declarative - 1.2
Property should be present only when the pipeline is declarative
- links to
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
So once https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/222 is merged and released (presumably in 1.2.5), every job that's ever had a Declarative run will have a DeclarativeJobAction on it. The action itself has nothing to it, it's just a marker.
|Remote Link||This issue links to "PR #222 (Web Link)" [ 18129 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
Code changed in jenkins
User: Andrew Bayer
[FIXED JENKINS-46252] Mark Declarative jobs with DeclarativeJobAction
If we are in a Declarative run, mark the parent job as a Declarative
job via DeclarativeJobAction, if it's not already present. Note that
we never remove this - if a job was ever once Declarative, we still
count it as such. Imperfect, but close enough.
|Status||Resolved [ 5 ]||Closed [ 6 ]|
So what's actually desired here, if I'm remembering correctly, is a JobProperty.