-
Bug
-
Resolution: Fixed
-
Medium
-
3.1.3
-
None
-
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.
- duplicates
-
-
- Closed
-
[BAM-9067] 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
Hemal Udani
added a comment - This is hindering our production environment. Does the Atlassian team have a ETA on the fix? I see that the issue was sumibtted a week ago. I dont see any comments from anyone. So, I am concerned and afraid that this may not be getting attention. We are a under-support customer and we just upgraded to bamboo 3.1.1 . Please provide a fix immediately.
Hemal Udani
added a comment - This is hindering our production environment. Does the Atlassian team have a ETA on the fix? I see that the issue was sumibtted a week ago. I dont see any comments from anyone. So, I am concerned and afraid that this may not be getting attention. We are a under-support customer and we just upgraded to bamboo 3.1.1 . Please provide a fix immediately. 
Hemal,
Bamboo 3.1.4 should have this fix in it and will be released early next week.
Cheers,
Mark C