Joerg Schwaerzler created JENKINS-12944:
-------------------------------------------
Summary: Env Inject Plugin doesn't substitute ${WORKSPACE}
variable at all when used in 'Preparing an environment for the job'
Key: JENKINS-12944
URL: https://issues.jenkins-ci.org/browse/JENKINS-12944
Project: Jenkins
Issue Type: Bug
Components: envinject
Affects Versions: current
Reporter: Joerg Schwaerzler
Assignee: gbois
Since we upgraded to EnvInject v1.30 we don't get our variable set if they are
dependend on ${WORKSPACE}.
Please check the job log snippet:
--------------------------------------------------------------
11:02:12 [EnvInject] - Preparing an environment for the job.
11:02:12 [EnvInject] - Jenkins system variables are kept.
11:02:12 [EnvInject] - Jenkins build variables are kept.
11:02:12 [EnvInject] - Injecting as environment variables the properties
content
11:02:12 HOME=${WORKSPACE}\home\muccctt1
11:02:12
11:02:12 [EnvInject] - Variables injected successfully.
11:02:12 [EnvInject] - Unset unresolved 'WORK_DRIVE' variable.
11:02:12 [EnvInject] - Unset unresolved 'HOME' variable.
--
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
