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

gbois commented on JENKINS-12691:
---------------------------------

I think it's due that ${LD_LIBRARY_PATH} is not already defined.
Could you try LD_LIBRARY_PATH=${AVARIABLE}/lib?
                
> Property variable not set if using a property file
> --------------------------------------------------
>
>                 Key: JENKINS-12691
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>    Affects Versions: current
>         Environment: Linux (RedHat), Jenkinx 1.446,  EnvInject 1.17
>            Reporter: Bruno L
>            Assignee: gbois
>
> I am trying to inject environment variables to the build process after SCM 
> checkout. If I point to a .properties file in the workspace some variables do 
> not get set properly while others are OK. If I copy/paste the content of the 
> file into the "Properties Content" box in the Jenkins project configuration 
> page then it works fine for all variables.
> For example
>    AVARIABLE=/some/path
>    PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
>    LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
> where I already have some existing directories in my $PATH. If I save this in 
> a file and point to it then I get errors :
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'PATH' variable.
> [EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
> But the same 3 lines work fine if I enter them directly in the "Properties 
> Content" dialog box

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