|
||||||||
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-14787) Perforce plugin does not substitute all variables when polling for new changes
berb...@cleverbridge.com (JIRA) Wed, 15 Aug 2012 00:20:29 -0700
- [JIRA] (JENKINS-14787) Perforce plugin doe... berb...@cleverbridge.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... berb...@cleverbridge.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... berb...@cleverbridge.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... berb...@cleverbridge.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-14787) Perforce plugi... jenk...@richardlee.name (JIRA)
What confuses me is the difference between polling and running a job. I would expect that the same variables are substituted in both cases. A list of supported variables for the fields "Perforce/Project Details/Workspace (client)" and "Perforce/Project Details/Client View Type/View Map" would be great.
The variable ${USERNAME} should be replaced with the user name that is used for connecting to Perforce (field "Perforce/Depot/Username"). Perhaps this variable should be named as ${P4USER}.
The use of ${nodename} in the 'client name format for slaves' option is a good workaround.