[JIRA] (JENKINS-42578) Parameters (from Properties) should have an option to keep the previous value

[r.baeris...@gmail.com (JIRA)]

Title: Message Title

Roman Baeriswyl updated an issue   Jenkins / JENKINS-42578 Parameters (from Properties) should have an option to keep the previous value Change By: Roman Baeriswyl To define parameters in a pipeline script (especially multi-branch), you need to use the properties step and define the parameters there. Unfortunately, the defaultValue defined there will always overwrite the value which might have been adjusted in the Jenkins Web UI. I currently use the following to keep the values: {code:java} properties([     // Parameters     parameters([         string(name: 'buildType', defaultValue: (params.buildType == null) ? 'Release' : params.buildType, description: 'Defines which build should be run (Release / Debug)'),         booleanParam(name: 'runUnitTests', defaultValue: (params.runUnitTests == null) ? true : params.runUnitTests, description: 'Defines if unit tests should be run')     ]) ]){code} As you see, in each defaulValue defaultValue I first check if it is not null and if so, use the previous value and only otherwise use the defaultValue. Would be great to either have the defaultValue to behave like this by default or have a flag: defaultOnlyIfNotSet or something like that. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.