[
https://issues.jenkins-ci.org/browse/JENKINS-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163551#comment-163551
]
aewallace commented on JENKINS-7978:
------------------------------------
To add to the above, I've also recently attempted to use a Buckminster script
file again with the latest Jenkins Buckminster plugin (1.10) after previously
using the normal entry of Buckminster command in my build configuration. I am
still finding that environment variables are not picked up, even using the
${env_var:WORKSPACE} nomenclature as described above.
The first entry in my script file is:
importtargetdefinition --active ${env_var:WORKSPACE}/path/subpath/bucky.target
The build always fails as the ${env_var:WORKSPACE} is never expanded (always a
blank string) and hence the full path that I need cannot be used as I just end
up with "/path/subpath/bucky.target" Am I missing something? Buckminster
version is 3.7.
> Variable substitution in Buckminster script file not respected
> --------------------------------------------------------------
>
> Key: JENKINS-7978
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7978
> Project: Jenkins
> Issue Type: Bug
> Components: buckminster
> Affects Versions: current
> Environment: Windows7
> Reporter: aewallace
> Assignee: jutzig
>
> When I used a script file including my Buckminster commands instead of
> entering the commands directly into the Buckminster command text area
> variable substitution does not appear to be respected.
> Thus, if I use something like ${WORKSPACE}/pathToSomething in the command
> enterted directly in the Buckminster text area , then the ${WORKSPACE}
> variable is substituted correctly to the Hudson workspace for the current
> job. However, if I use the same variable within my Buckminster script file,
> then a blank string is substituted instead when the command is run.
--
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
