|
||||||||
|
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 have managed to find one work around. p4 logout -a on the master server, then run the offending job in Jenkins to force a p4 login. This appears to kick-start the use of the p4 ticket and the creation of the P4TICKET variable again.