[JIRA] (JENKINS-60459) Pipeline parameters not properly updated in multibranch job config

[allan.le...@youview.com (JIRA)]

Title: Message Title

Allan Lewis created an issue   Jenkins / JENKINS-60459 Pipeline parameters not properly updated in multibranch job config Issue Type: Bug Assignee: Andrew Bayer Attachments: plugins.txt Components: pipeline-model-definition-plugin Created: 2019-12-12 11:29 Environment: Jenkins 2.176.2 Plugins: see attached plugins.txt Priority: Major Reporter: Allan Lewis I have a multi-branch pipeline where I've replaced a boolean parameter with a choice parameter but the "build with parameters" page shows the old boolean parameter; this is after I've done a dummy run to pick up the change. The log reports that it read the pipeline from the latest commit on that branch (master) which has the parameter change. In branches/master/config.xml, I see that the new parameter is listed in the parameters element, but the definition in parameterDefinitions is the old one! Here's an excerpt of that file - the old parameter is named REBOOT_FIRST and the new one is REBOOT_WHEN: branches/master/config.xml <flow-definition plugin="workflow-job@2.33"> <actions> ... <org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction plugin="pipeline-model-definition@1.3.9"> ... <parameters> <string>REBOOT_WHEN</string> ... </parameters> ... </org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction> </actions> ... <properties> <hudson.model.ParametersDefinitionProperty> <parameterDefinitions> <hudson.model.BooleanParameterDefinition> <name>REBOOT_FIRST</name> <description>...</description> <defaultValue>true</defaultValue> </hudson.model.BooleanParameterDefinition> ... (I've elided various irrelevant bits with '...') So it seems like the first list has been updated, but the actual definition hasn't. THis has left me with a broken pipeline that I can't recover without editing config.xml manually and restarting Jenkins; I haven't yet tried this but I expect it to work. If updating any plugins would help, please advise and I'll try that, subject to my sysadmin approving. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203537.1576150173000.6289.1576150200230%40Atlassian.JIRA.