Andrew Bayer
added a comment - 2017-11-21 15:29 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.

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.

SCM/JIRA link daemon
added a comment - 2017-11-21 16:55 Code changed in jenkins
User: Andrew Bayer
Path:
pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/RuntimeASTTransformer.groovy
pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/actions/DeclarativeJobAction.java
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/4ef849e15f96ec234fe39d7314a27789d3eb8bee
Log:
[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.