Setting custom PATH on a task for a remote agent, the PATH environment variable is being overwritten when the task launches by the remote agents' own path

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 3.1.4, 3.2 M3, 3.2
    • Affects Version/s: 3.1.3
    • Component/s: Bamboo Release
    • None
    • Environment:

      standalone
      Windows XP x86
      JDK 1.6.0_12

      I just installed 3.1.3 and upgraded from Bamboo 3.0.
      I was working on a new script to take advantage of the Task system that was added in the new version.

      It happens on an Ant task on the first stage of a build job.

      On the Task Configuration dialog on the optional line for Environment Variables I specify a few custom environment variables and I also specify a custom Path variable to accomodate different build environments on different projects.

      When I tell the plan to run it fails because some tools can't be found in the path. In the build log I can see that the "Path" variable has been set twice and it looks like the second time it's being set it's overwriting the custom path data I had specified.

            Assignee:
            Marcin Gardias
            Reporter:
            Jay Barra
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: