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

Gabriele Giuseppini edited comment on JENKINS-13157 at 3/21/12 2:45 PM:
------------------------------------------------------------------------

Same here. I have a variable defined as:
DBName=Jenkins${SVN_REVISION}

And after upgrading from 1.0 to 1.40, EnvInject stopped creating the new 
variable.

Uh, sorry - after reading the latest comments, I need to clarify that I'm 
trying to get EnvInject to *resolve* the nested variables, with no luck in 1.40.
                
      was (Author: gabrielegiuseppini):
    Same here. I have a variable defined as:
DBName=Jenkins${SVN_REVISION}

And after upgrading from 1.0 to 1.40, EnvInject stopped creating the new 
variable.
                  
> EnvInject cannot inject variables whose contents contain a dollar sign ($)
> --------------------------------------------------------------------------
>
>                 Key: JENKINS-13157
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13157
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>            Reporter: David Baumgold
>            Assignee: gbois
>
> If I add an variable in the Jenkins configuration with a dollar sign in the 
> content, then the variable is not injected. The console output says that the 
> variable is unset because it is "unresolved":
> {code}
> [EnvInject] - Executing scripts and injecting environment variables after the 
> SCM step.
> [EnvInject] - Injecting as environment variables the properties content 
> ADMIN_PASS="pas$word"
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'ADMIN_PASS' variable.
> {code}
> I've tried single quotes and double quotes, escaping with \$ and with $$, and 
> nothing works: every time, the variable is unset. Help?

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