Variable substitution in Buckminster script file not respected

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major
    • Component/s: buckminster-plugin
    • None
    • Environment:
      Windows7

      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.

            Assignee:
            jutzig
            Reporter:
            aewallace
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: