|
||||||||
|
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 a test job to show the problem:
Building remotely on gb-mlb-pm-002 (linux) in workspace /var/lib/jenkins/workspace/Trigger TOOLS MA_SW_ci_tools
Using remote perforce client: Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078
[Trigger TOOLS MA_SW_ci_tools] $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 workspace -o -S //MA_SW/ci_tools Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078
[Trigger TOOLS MA_SW_ci_tools] $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 login -a -p
[Trigger TOOLS MA_SW_ci_tools] $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B workspace -o -S //MA_SW/ci_tools Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078
Last build changeset: 50593
[Trigger TOOLS MA_SW_ci_tools] $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B changes -s submitted -m 1 //Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078/...
Sync'ing workspace to changelist 50593.
[Trigger TOOLS MA_SW_ci_tools] $ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s sync //Trigger_TOOLS_MA_SW_ci_tools_jenkins_mlb-2062542078/...@50593
Sync complete, took 752 ms
[Trigger TOOLS MA_SW_ci_tools] $ /bin/sh -xe /tmp/hudson3065486592967532870.sh
+ /u-blox/gallery/perforce/p4/lin_64/2013.3/bin/p4 describe 48315
Perforce password (P4PASSWD) invalid or unset.
Build step 'Execute shell' marked build as failure
I can see a line: p4 login -a -p
Which , according to:
http://www.perforce.com/perforce/doc.current/manuals/cmdref/p4_login.html
"-p Display the ticket, rather than storing it in the local ticket file."
The authentication ticket is then used in later steps: -P CB36E3E1DC213D9D0161CA6FF7C5309B
So either the ticket value needs to be exposed to later Job steps can used it via some variable.
Or the ticket needs to be stored in a local ticket file.
(http://www.perforce.com/perforce/doc.current/manuals/cmdref/P4TICKETS.html)