Corey O'Brien created JENKINS-13951: ---------------------------------------
Summary: Custom workspace not resolved correctly after installing EnvInject Key: JENKINS-13951 URL: https://issues.jenkins-ci.org/browse/JENKINS-13951 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: windows Reporter: Corey O'Brien Assignee: Gregory Boissinot Attachments: config.xml, slaveconfig.xml 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: {noformat} [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 {noformat} This may or may not be related to JENKINS-12027 which was resolved as fixed in 1.2 without confirmation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira