[ 
https://issues.jenkins-ci.org/browse/JENKINS-12841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159401#comment-159401
 ] 

SCM/JIRA link daemon commented on JENKINS-12841:
------------------------------------------------

Code changed in jenkins
User: Gregory Boissinot
Path:
 src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
 
src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter.java
http://jenkins-ci.org/commit/envinject-plugin/b2c132e077b2bb052df175660a8906533d681d37
Log:
  Fix JENKINS-12704 and JENKINS-12841


Compare: https://github.com/jenkinsci/envinject-plugin/compare/6ff47b2...b2c132e


                
> EnvInject Plugin 1.26 does not substitute ${WORKSPACE} correctly
> ----------------------------------------------------------------
>
>                 Key: JENKINS-12841
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12841
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>            Reporter: mwebber
>            Assignee: gbois
>            Priority: Critical
>         Attachments: config.xml
>
>
> This problem appeared when I upgraded the EnvInject Plugin from 1.25 to 1.26, 
> so the problem was probably introduced with the fix for JENKINS-12704.
> I have a job with "Inject environment variables to the build process" 
> selected, and the following line in "Properties Content":
> materialize_workspace_path=${WORKSPACE}/materialize_workspace
> In 1.25, this environment variable was correctly given the value
> {{/scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}
> In 1.26, this environment variable was WRONGLY given the value
> {{/scratch/jenkins_slave//scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}

--
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

        

Reply via email to