[
https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160041#comment-160041
]
gbois commented on JENKINS-13022:
---------------------------------
I tried with version 1.454 and I'm afraid I didn't reproduce the issue.
Could you attach your job descriptor (config.xml - found in
$JENKINS_HOME/jobs/<job_name>/config.xml)?
I'll try to reproduce it with your configuration.
Thanks
Gregory
> 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
>
> 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
