|
||||||||||||||
|
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 pl... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)
- [JIRA] (JENKINS-16233) EnvInje... [email protected] (JIRA)

Were you able to replicate the issue? We have upgraded to 1.80 and still see the issue. I've taken a look at the changes and not sure that 'we set a global workspace at job level' is accurate for what we are doing. We are setting an environment variable to the value including ${WORKSPACE} and instead of getting the job workspace it is the value of a previous job's workspace...