[
https://issues.jenkins-ci.org/browse/JENKINS-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159575#comment-159575
]
Rob Petti commented on JENKINS-12902:
-------------------------------------
Yes this is the desired behavior. Any changes that are found during polling
will launch the build with the default values anyways, so it only makes sense
to poll using the default values.
> Polling operation overrides client mappings with default parameters (for
> parametrized job with default values)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12902
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12902
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Reporter: Mikko Tapaninen
>
> If a job is parametrized with default parameter values and if the job uses
> these parameters in it's view map, then the polling operation always saves
> the workspace view maps again by using the default parameter values. So if
> you've forced a build with different parameter values, the next polling
> operation will overwrite the mappings in your workspace back to the "default"
> values.
> Is this a desired behavior? Shouldn't the polling just query the workspace
> object and see if there are changes?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
