[
https://issues.jenkins-ci.org/browse/JENKINS-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160619#comment-160619
]
Gabriele Giuseppini commented on JENKINS-13183:
-----------------------------------------------
Attached (I've anonymized sensitive information).
Please note that this is the config with EnvInject 1.0 and Jenkins 1.456 (i.e.
the configuration that resolves the variable). Here's an excerpt from the log
that shows the variable being successfully injected:
[EnvInject] - Injecting as environment variables the properties content
CIDBName=Jenkins226253
> 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
