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
-
-
- Open
-
Activity
Karl,
I did the workaround as suggested on the jenkin master 'Configure System' by adding P4CLIENT to the "Global properties" as follows. It worked.
Name: P4CLIENT
Value: $P4_CLIENT
I'm wondering if the Jenkins Guild below should also mention this issue for "Freestyle jobs configured for P4"
Helix Plugin for Jenkins Guide (1.10.x), Freestyle job - Manual Workspace setup
https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/workspace-manual.html
Thanks again.
David
Hi David Rodriguez - Aha. Another Jenkins feature I never knew about. Thanks. Great that it's now working and thanks for correcting the typos in the other job.
Yes I agree this should be documented so passed this job to our doc team. I'm going to suggest the following wording, but they will tweak it as needed to match the documentation standards and correct grammar:
Note that when using build steps such as 'Execute Shell' the standard Perforce variables P4PORT, P4USER and P4CLIENT are not set in the environment. This is to ensure the plugin does not overwrite variables on preconfigured build environments. If a build step needs access to these values the variables P4_PORT, P4_USER and P4_CLIENT can be used. For example in a shell script: export P4CLIENT=$P4_CLIENT To make the standard variables accessible by default they can be set in the 'Global properties' section on the Jenkins 'Configure System' page. For example:
Karl Wirth
added a comment - Hi David Rodriguez - Aha. Another Jenkins feature I never knew about. Thanks. Great that it's now working and thanks for correcting the typos in the other job.
Yes I agree this should be documented so passed this job to our doc team. I'm going to suggest the following wording, but they will tweak it as needed to match the documentation standards and correct grammar:
Note that when using build steps such as 'Execute Shell' the standard Perforce variables P4PORT, P4USER and P4CLIENT are not set in the environment. This is to ensure the plugin does not overwrite variables on preconfigured build environments. If a build step needs access to these values the variables P4_PORT, P4_USER and P4_CLIENT can be used. For example in a shell script:
export P4CLIENT=$P4_CLIENT
To make the standard variables accessible by default they can be set in the 'Global properties' section on the Jenkins 'Configure System ' page. For example:
Ready for release
Released
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.