In my repositories, there are scripts that use the $HOME environment variable. The problem is, that although this variable is set properly on the agent in a normal shell, it isn't set when I run a script task.
Is there an easy way to make the variable available?
Using a global variable only defines bamboo_HOME and writing it in the environment field for each task isn't realy an option because there are too many scripts.
I have run a test on both remote and local agents and it seems the $HOME environment variable is read succesfully. If it does not work for you, check the build logs http://confluence.atlassian.com/display/BAMBOO/Logging+in+Bamboo to see if there is any error thrown that might give us a clue.
The workaround of using the global variable is feasible if you can call the variable something elase rather than HOME to avoid confusing with the default bamboo_HOME
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot