Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: p4-plugin
-
Environment:OS: Ubuntu 18.04
JDK 1.8.0_181
P4 Plugin v
Jenkins v2.222.1
P4 Plugin v1.10.12
Jenkins master in container (image: jenkins/jenkins:2.222.1)
Jenkin slaves in container (image: jenkins/jnlp-slave:3.27-1)
-
Similar Issues:
Description
Getting error message "must create client 'ip-10-21-2-84' to access local files".
It appears when the job is executed on the jenkins slave the P4 client is not being created. Does the p4 plugin create the workspace and manages the workspace view. Or does the p4 plugin require an additional setup that I might be missing.
- Job Configuration: Reference attached job config.xml
- Build log attached.
Note that I also tested the job on a jenkins slave that was not in a container. Got the same error. When I ran 'p4 client' and set-up the root and mapping, the jenkins job worked.
Attachments
Issue Links
- is caused by
-
JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
-
- Open
-
Hi David Rodriguez - Thanks for those kind words.
The developers have confirmed that 1.3.35 was the old community plugin. That did set the variables. The new plugin developed by Perforce has never set the variables because we were worried about stamping on environment variables that had been preconfigured already on build slaves.
I have therefore raised the following enhancement request:
https://issues.jenkins-ci.org/browse/JENKINS-62008
The workaround would still be the same that you need to manually set P4CLIENT in the build script based on P4_CLIENT.