-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
windows
After installing EnvInject, existing jobs that have no EnvInject settings enabled are broken if they use a custom workspace. When running a job with a custom workspace on a slave, the custom workspace is ignored and %WORKSPACE% is set to the slave's root instead. Job configuration and the snippet from the jenkins config for the slave are attached.
This is running with Jenkins 1.461 and EnvInject 1.54
Here's the console output from the attached job:
[EnvInject] - Loading node environment variables. Building remotely on Master-Admin in workspace C:\envinjcustomws [envinjcustomws] $ cmd /c call C:\Users\jenkins\AppData\Local\Temp\hudson867880511665494930.bat C:\envinjcustomws>echo C:\Jenkins_AdminNode C:\Jenkins_AdminNode C:\envinjcustomws>exit 0 Finished: SUCCESS
This may or may not be related to JENKINS-12027 which was resolved as fixed in 1.2 without confirmation.
[JENKINS-13951] Custom workspace not resolved correctly after installing EnvInject
Gregory Boissinot
added a comment - I'm terribly sorry but I can't reproduce the issue in my environment.
I'm closing for now the issue.
Please do not hesitate to reopen it if the issue persists and you have more information.
Thanks in advance.
Gregory Boissinot
added a comment - I'm terribly sorry but I can't reproduce the issue in my environment.
I'm closing for now the issue.
Please do not hesitate to reopen it if the issue persists and you have more information.
Thanks in advance. 
Are you sure?
I'm afraid I can't reproduce.