Bamboo seems to ignore my system environment variables which makes some of the tasks fail (composer). I'm running Bamboo 5.6.
I'm essentialy running a "command" task in one of my builds. This runs composer for dependency management and it expects to find a $HOME env variable set.
My bamboo runs through it's own user and when I log in locally I find my env variables just fine. But when bamboo runs they seem to never be set.
I found the following : https://confluence.atlassian.com/display/BAMKB/Bamboo+does+not+pick+up+the+Path+environment+variable+correctlybut I don't know if it's related because I used to test run a bamboo 5.5.x with a similar setup and that worked just fine (though it was running as root.. so maybe the above does apply but I can't set HOME globally)
Any ideas how I could work around this? I'm lost as to what to do.
Ok I had an idea as this worked. realized that command tasks had an env field. So even though it's tedious I'm using that as a workaround for the moment. Can any of you confirm this is related to the bug I linked?
Here's more information on how I solved this in the event it can help anyone:
When setting up the tasks, there's an Environment variables field that can be configured. You can use this to work around the issue.
Capture d’écran 2014-09-24 à 18.44.49.png
As you can see above, I've configured it to use /home/bamboo (my bamboo user home folder) as the $HOME env variable.
Like I mentioned in my original post. It can become quite tedious, but at least it works.
Hope it helps
I got it solved through customer support and eventually the reason appeared to be a wrong init.d script that starts Bamboo. In my case, I had an erroneous line in my script as follows:
start) echo "Starting $APP" /bin/su -m $USER -c "cd $BASE/logs && $BASE/bin/startup.sh &> /dev/null" ;;
There "-m" part was wrong. The final, solution answer from Support was as following, which solved my problem:
Alright.. I think we have got the root cause. The reason for this behavior is that the startup script uses the/bin/su -m $USER -c
Notice the "-m", This means that the environment variables are preserved. So when you change the user to "bamboo", we didn't capture the environment variables from that user but rather, we just use the variables of the user logged in. Please edit the script and remove the "-m" option. This should fix the issue with next reboot. For more information and updated script, please refer to https://confluence.atlassian.com/display/BAMBOO/Running+Bamboo+as+a+Linux+service
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