|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I think I may have found a reasonable workaround. Before running the build step, I simply set P4USER to the proper user and P4CLIENT to $P4_CLIENT; then perform a p4 login. I use the mask passwords plugin to ensure that the Perforce user's password is not exposed. I'm not really a fan of having to place the same password in two places though. You may also need to set P4PORT (depending on how the node the build runs on is configured).