|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-7162) specifying a cli para... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)
- [JIRA] (JENKINS-7162) specifying a cli... [email protected] (JIRA)

Pull request PULL 540 added to fix this.[1]
Add all the job defined Parameters to the ParameterAction using Defaults
if not passed via the command line.
If this breaks backwards compatibility where these are not expected to be passed, we can introduce a new option to use the defaults for parameters which triggers this behaviour.
@Option(name="-d",usage="Use defaults for parameters not specified, only valid when -p is used")
public boolean parameterDefaults = false;
[1] https://github.com/jenkinsci/jenkins/pull/540