[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161165#comment-161165 ]
lestin commented on JENKINS-13270: ---------------------------------- Ah, maybe that's where the confusion is. Below description is based on Linux BTW. Perforce can create a p4 ticket file (normally |/.p4ticket) that remembers your login if you use "p4 login -a" Once that's setup (you can setenv P4TICKET to change the default file path), p4 will check the file to see if this user had been id-cleared. In my setup, I configured jenkins_home/.p4ticket and it has registered my success login (p4 login -a with my user id). With this, jenkins can access the perforce database as if it were me (or any one else that has registered himself in jenkins_home/.p4ticket). Now at the job configuration page, i configured it as normal (correct combination of user id, passwd). If this user id has been registered in jenkins_home/.p4ticket, the passwd can be a wrong one, no issue at all. If this user id has not been registered in jenkins_home/.p4ticket, even the correct combination will caused a login error with the line "Perforce password (P4PASSWD) invalid or unset." --- Note that this line is from the web page, not the jenkins.log I tried to set P4PASSWD variable in the environment var field, tick the box in job configuration etc, none of them worked. If i put an invalid user id, the plugin immediately informs me that. > 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