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

2013-01-15 Thread bsilverb...@mozilla.com (JIRA)














































Bob Silverberg
 commented on  JENKINS-16233


EnvInject plugin using a cached value for ${WORKSPACE}















The value is not specified anywhere else in the job nor in the global configuration. It seems to be caching the workspace value that was used for a previous job.



























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






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

2013-01-08 Thread bsilverb...@mozilla.com (JIRA)














































Bob Silverberg
 commented on  JENKINS-16233


EnvInject plugin using a cached value for ${WORKSPACE}















This problem went away for about a week after rebooting a few times but just cropped up again. Any help that anyone can provide would be greatly appreciated.



























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






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

2013-01-01 Thread bsilverb...@mozilla.com (JIRA)














































Bob Silverberg
 created  JENKINS-16233


EnvInject plugin using a cached value for ${WORKSPACE}















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


envinject



Created:


01/Jan/13 3:07 PM



Description:


Starting yesterday, the EnvInject plugin seems to suddenly start using a cached value for ${WORKSPACE}. We have the following value in "Properties Content" under "Inject environment variables to the build process":

PATH=${WORKSPACE}/.env/bin:$PATH

When working properly, in the console output this appears as:

EnvInject - Injecting as environment variables the properties content 
PATH=${WORKSPACE}/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/bin

Over the past couple of days this has suddenly started appearing as:

EnvInject - Injecting as environment variables the properties content 
PATH=/Users/Shared/Jenkins/Home/jobs/bidpom.stage/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/bin


Which is using a workspace path from another job. This causes this job, and all other jobs, to fail. If I restart Jenkins the problem goes away, for awhile, but at some point that exact same path starts getting used by the EnvInject plugin again.  This cycle has happened 4 times over the past couple of days, where jobs will run fine for awhile and then suddenly start failing because the path injected changes from:

${WORKSPACE}/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/bin

to:

/Users/Shared/Jenkins/Home/jobs/bidpom.stage/workspace/.env/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/bin

When this first happened we downgraded the plugin from 1.78 to 1.77 but this hasn't addressed the problem.

Any help anyone can provide would be greatly appreciated.




Project:


Jenkins



Priority:


Major



Reporter:


Bob Silverberg

























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