|
||||||||
|
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-11786) Could we use masked ... [email protected] (JIRA)
- [JIRA] (JENKINS-11786) Could we use ma... [email protected] (JIRA)
- [JIRA] (JENKINS-11786) Could we use ma... [email protected] (JIRA)
- [JIRA] (JENKINS-11786) Could we use ma... [email protected] (JIRA)

Tried it as a mask password, too. Doesn't work. Am using the latest versions of jenkins and the perforce plugin (1.470 and 1.3.15). Have you seen this actually work? It does not seem like it is doing parameter substitution in the password field of the perforce plugin for the jenkins job. It would be great if there were a way to print out what it thought the password were in the output to tell for sure, but it never gets far enough to run any of my build scripts.