[JIRA] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}

[dave.h...@gmail.com (JIRA)]

Dave Hunt commented on JENKINS-16233 EnvInject plugin using a cached value for ${WORKSPACE} This is happening right now. We need to restart Jenkins to fix this, but it will no doubt happen again. I've done a little investigation and found that echoing ${WORKSPACE} in a build shell shows the correct value, but EnvInject has injected the wrong value: [CHECKED] Inject environment variables to the build process Properties Content: TEST=${WORKSPACE} PATH=${WORKSPACE}/.env/bin:$PATH Execute shell: printenv echo ${WORKSPACE} echo ${PATH} Console output: ... [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content TEST=/Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace PATH=/Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin [EnvInject] - Variables injected successfully. ... + printenv ... TEST=/Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace WORKSPACE=/Users/Shared/Jenkins/Home/jobs/bouncer.prod/workspace PATH=/Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin ... + echo /Users/Shared/Jenkins/Home/jobs/bouncer.prod/workspace /Users/Shared/Jenkins/Home/jobs/bouncer.prod/workspace + echo /Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin /Users/Shared/Jenkins/Home/jobs/bidpom.stage.saucelabs/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin So you can see that WORKSPACE is accurate according to Jenkins environment variables, but EnvInject is expanding it to an incorrect value. Please let me know if there's any additional information that would be useful for the next time this fails.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira