![]() |
|
|
Issue Type:
|
Bug
|
Affects Versions:
|
current |
Assignee:
|
Unassigned |
Components:
|
perforce |
Created:
|
30/Oct/12 3:06 PM
|
Description:
|
[BTW, Thanks for your help and efforts with the P4 plugin. It is a fantastic tool!]
Using a parameterized build I can set a string parameter X to a string value then reference ${X} in the Perforce workspace form where it resolves at build time to the value of ${X}.
Alternately, using choice parameters (having pre-defined values) I set the value of X in the Perforce workspace form (or view) and it does not resolve the value, but rather passes it as a literal string: "${X}".
The ability to resolve choice parameters seems to be a valuable functionality to have.
|
Environment:
|
Jenkins 1.488, Perforce plugin 1.3.17, 64-bit Windows OS, JRE 1.6.0.33, Tomcat 5.5
|
Project:
|
Jenkins
|
Labels:
|
scm
plugin
|
Priority:
|
Major
|
Reporter:
|
Tom Greer
|
|
|
|
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-15667) Choice parameters not pa... tgr...@vocera.com (JIRA)
-