[
https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160044#comment-160044
]
SCM/JIRA link daemon commented on JENKINS-13022:
------------------------------------------------
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper.java
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuilder.java
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/bf15513e57f910d0376bca9f4f9c22cf1966d637
Log:
Fix JENKINS-13022
> EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
> -------------------------------------------------------
>
> Key: JENKINS-13022
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13022
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
> Reporter: Jim Searle
> Assignee: gbois
> Attachments: config.xml
>
>
> I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not
> being set. I downgraded envinject to 1.31 and it worked again.
> I'm using "Prepare an environment for the job" "Properties Content" section
> and have "Keep Jenkins Environment Variables" and " Keep Jenkins Build
> Variables" enabled.
--
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
