| We noticed that the parameter block of our job's config.xml sometime gets cleared when a sub job is created. Example Before: <?xml version='1.0' encoding='UTF-8'?>
<flow-definition plugin="workfl...@2.17">
<actions>
<org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobAction plugin="pipeline-mod...@1.2.7"/>
<org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction plugin="pipeline-mod...@1.2.7">
<jobProperties/>
<triggers/>
<parameters/>
</org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction>
</actions>
<description></description>
<keepDependencies>false</keepDependencies>
<properties>
<hudson.model.ParametersDefinitionProperty>
<parameterDefinitions>
<hudson.model.TextParameterDefinition>
<name>REQUEST_DATA</name>
<description></description>
<defaultValue></defaultValue>
</hudson.model.TextParameterDefinition>
</hudson.model.ParametersDefinitionProperty>
</properties>
<definition class="org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="workfl...@2.45">
<scm class="hudson.plugins.filesystem_scm.FSSCM" plugin="filesystem_scm@2.1">
<path>jenkins.groovy.scripts.path</path>
<clearWorkspace>false</clearWorkspace>
</scm>
<scriptPath>flavour.groovy</scriptPath>
<lightweight>true</lightweight>
</definition>
<triggers/>
<disabled>false</disabled>
</flow-definition> After <?xml version='1.0' encoding='UTF-8'?>
<flow-definition plugin="workfl...@2.17">
<actions>
<org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobAction plugin="pipeline-mod...@1.2.7"/>
<org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction plugin="pipeline-mod...@1.2.7">
<jobProperties/>
<triggers/>
<parameters/>
</org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction>
</actions>
<description></description>
<keepDependencies>false</keepDependencies>
<properties>
</properties>
<definition class="org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="workfl...@2.45">
<scm class="hudson.plugins.filesystem_scm.FSSCM" plugin="filesystem_scm@2.1">
<path>jenkins.groovy.scripts.path</path>
<clearWorkspace>false</clearWorkspace>
</scm>
<scriptPath>flavour.groovy</scriptPath>
<lightweight>true</lightweight>
</definition>
<triggers/>
<disabled>false</disabled>
</flow-definition> Once it happens for the first time, it seems to happen consistently until jenkins is restarted entirely and the config.xml file restored from a source repository. However, given that we have to restart jenkins, we potentially have to wait for other jobs to finish which can result in productivity loss on the team. If this is a known issue, can you point me at the correct jira. |
