-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: perforce-plugin
-
Labels:None
-
Environment:perforce plugin version: 1.3.33
OS: windows
web browser: all
JAVA version:1.7.0_25
CI Architecture: master-slave
-
Similar Issues:
If the credential for job is P4 ticket auth, we cannot sync the source code from P4, and get the error below. But the non-ticket auth credential can be used to sync source code from P4 correctly.
It seems current perforce plugin don't support P4 ticket authentication.
ERROR:
----------------------------------------------------------------
[EnvInject] - Loading node environment variables.
Building remotely on Slave31 (SlaveGroup3) in workspace C:\CI\workspace\Src-Main
Using remote perforce client: Beacon-Src-Main-461461931
[Src-xxx] $ p4 workspace o Beacon-Src-Main-461461931
[Src-xxx] $ p4 login -a -p
[Src-xxx] $ p4 workspace o Beacon-Src-Main-461461931
Caught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset.
at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:406)
at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:301)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1641)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1602)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:907)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1265)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1718)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
ERROR: Unable to communicate with perforce. Perforce password (P4PASSWD) invalid or unset.
Skipped archiving because build is not successful
Sending e-mails to: xxx@xxx.com
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
I'm not a Perforce expert, anyway when I use the command line and I do the p4 set P4PORT:myserver and than I can do the login whiteout any problem. Note I'm not interest to use the ticket, but I don't understand Jenkins is forcing to use this option. It seems that Jenkins plugin doesn't pass the password information.
Note: I also have a Perforce that I use as test server (on this server I don't use the ssl protocol), and the perforce plugin on Jenkins works fine.
Thanks in advance.