[
https://issues.jenkins-ci.org/browse/JENKINS-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-13183.
-----------------------------
Resolution: Fixed
Could you test the fix with EnvInject 1.42?
Do not hesitate to reopen the issue with your comments if this new version
doesn't fix the issue in your context.
Thanks
> EnvInject 1.40 does not resolve anymore environment variables in values of
> environment variables
> ------------------------------------------------------------------------------------------------
>
> Key: JENKINS-13183
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13183
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
> Affects Versions: current
> Environment: Windows Server 2008, Jenkins 1.456. List of plugins
> attached.
> Reporter: Gabriele Giuseppini
> Assignee: gbois
> Attachments: config.xml, Plugins.csv
>
>
> Most of our jobs had EnvInject variables like the following:
> DATABASE_NAME=JenkinsFooBar${SVN_REVISION}
> These were happily resolved until we upgraded EnvInject from 1.00 to 1.40,
> and Jenkins itself from 1.435 to 1.456. After the upgrade, EnvInject logs an
> error saying that variable DATABASE_NAME is unresolved.
--
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
