Degraded performance Customers may experience issues using Community search. Our team is investigating.
Bamboo task failed with error "/usr/local/git/libexec/git-core/git-sh-setup: line 235: uname: command not found". The command is present on the server, i can also ran every command from Bamboo task on the server without any problem or errors. Bamboo uses the same user credentials but trows the error above and exits with "Result: exit code = 255"
How can i solve this problem.
I did but still same problem.
The Bamboo task looks like this.
git checkout Acceptance
git fetch --all --recurse-submodules=on-demand -v
git reset --hard Acceptance
git submodule sync
git submodule update --init --recursive --force
All the commands can be executed in same order (1 by 1 ) on the server without any problem.
These were the info i could find about the instance in the log:
simple 21-Jan-2016 14:15:26 Build GGD Zuid Limburg - ggdzl.acceptance.netcreators.nl - Default Job #17 (GGDZLB-GGDZLAC-JOB1-17) started building on agent Elastic Agent on i-0f7ca4365351a4ce6 simple 21-Jan-2016 14:15:26 Elastic agent on instance i-0f7ca4365351a4ce6
If i'm not mistaken it's a remote instance. Bamboo will start a instance when ever there's a task to be executed.
How can i fix the permission because Bamboo will create a new instance when needed.
So i could fix it on a instance but when this instance is no longer required (has gone into idle state for a long period) Bamboo will terminate it. And when there is a new task to be executed Bamboo will create a new instance.
I've tried both.
On the actual server where the repo files are stored. I can execute uname in any directory including the ones from Bamboo task job.
Also on the elastic server i could execute the uname command without any problem.
On other servers i don't get this uname error, the task commands are the same (only the ip-address and username are different).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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