[
https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161175#comment-161175
]
lestin commented on JENKINS-13270:
----------------------------------
Hi Rob,
"I recommend unsetting P4TICKETS to ensure that the same tickets file
(~/.p4tickets) is used by the build process and the perforce plugin login
operation"
^^^It is configured to the same ticket file.
However, the use case here is, jenkins is running of one account but the jobs
are setup by different engineers.
Unless the jenkins .p4ticket contains all the user entries, it won't be able to
achieve that.
//unless the plugin does a "p4 login -a" to add user entry, which it doesn't
seem to be doing now.
I think i've found the reason it doesn't work with the P4PASSWD in our server
setup when we have the expose box ticked.
The variable being set in the environment variable P4PASSWD is the user input
whilst it should be the hash passwd like the one you used in the plugin (p4 -P
...).
I tried to do an "echo $P4PASSWD" and i got the passwd in plain text instead of
the hash ones like "687A2F0323B3C666D6C69E5E2F78B665"
Lestin
> Occasional login failures using p4 ticket
> -----------------------------------------
>
> Key: JENKINS-13270
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13270
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Affects Versions: current
> Environment: 1.456 Jenkins with latest perforce plugin
> Reporter: lestin
> Assignee: Rob Petti
> Priority: Minor
>
> Saw the following log whilst nothing has changed during the period:
> ========================================
> INFO: job_name_here #4437 main build action completed: SUCCESS
> Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:18 AM hudson.model.Run run
> INFO: job_name_here #4438 main build action completed: SUCCESS
> Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login
> attempt failed: Password invalid.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Attempt to workaround p4 executable location failed
> com.tek42.perforce.PerforceException: Could not run perforce command.
> at
> hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
> at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
> at
> hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325)
> at
> hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019)
> at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
> at hudson.scm.SCM.poll(SCM.java:373)
> at hudson.model.AbstractProject.poll(AbstractProject.java:1340)
> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
> at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
> at
> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.IOException: Cannot run program "/usr/bin/p4" (in
> directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No
> such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
> at hudson.Proc$LocalProc.<init>(Proc.java:244)
> at hudson.Proc$LocalProc.<init>(Proc.java:216)
> at hudson.Launcher$LocalLauncher.launch(Launcher.java:707)
> at hudson.Launcher$ProcStarter.start(Launcher.java:338)
> at
> hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79)
> ... 19 more
> Caused by: java.io.IOException: java.io.IOException: error=2, No such file or
> directory
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
> at java.lang.ProcessImpl.start(ProcessImpl.java:65)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
> ... 24 more
> Problem: Login attempt failed: Password invalid.
> Mar 27, 2012 7:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 8:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 8:01:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 8:01:12 AM hudson.model.Run run
> INFO: job_name_here #4439 main build action completed: SUCCESS
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
