-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows
If the environment variable is assigned a value before the Jenkins slave starts the value is not changed by the plugin.
The P4CLIENT problem is visible, when a system level P4CLIENT is defined and the slave is run as a service as a user (MYDOMAIN\BUILDUSER) not as SYSTEM. If the build now uses this slave, perforce plugin cannot override P4CLIENT variable.
Can you give me more detail about your environment? I'm mostly looking for specific slave OS information, and JVM versions for master and slave.
Have you verified this behavior by adding a separate build action that does nothing but echo the P4CLIENT env variable? What sort of build actions are you using?