|
||||||||
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 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)
Generally environment variables are not using in plugin configuration, only build parameters, that's why it's undocumented. Feel free to update it, and I'll see if I can add the substitutions you requested. Granted, P4USER will always be constant, so it shouldn't even need to be defined as a parameter reference in your job configuration.