[ https://issues.jenkins-ci.org/browse/JENKINS-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163137#comment-163137 ]
Lorenzo Bettini commented on JENKINS-7978: ------------------------------------------ even with ${env_var:WORKSPACE} it still does not work... > 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