Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: p4-plugin
-
Labels:None
-
Environment:Win32 (should be any os)
-
Similar Issues:
Description
On builds that are distributed to nodes the Perforce plugin puts the master's client spec name in the P4CLIENT (was PCLIENT) environment variable instead of the node's clientspec name. I believe this is because the buildEnvVars function is called before getPerforceWorkspace.
Code changed in hudson
User: : rpetti
Path:
trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java
https://hudson.dev.java.net/source/browse/hudson/trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java?view=diff&rev=26139&p1=trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java&p2=trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java&r1=26138&r2=26139
http://jenkins-ci.org/commit/26139
Log:
[FIXED JENKINS-5332] refactored P4CLIENT environment variable to pass in modified client name when building on remote nodes