Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bamboo bash file-script task requires another task with chmod +x for that file

Deleted user Apr 10, 2020

Hi all,


Running on Bamboo 6.10.4 build 61009 - 21 Nov 19.


I have a bamboo build plan that gets some stuff from GIT as a first task, then starts this inline bash script task:


. ./api/ "$@"
exit "$?"

The above works fine. The /api/ script file that it starts is taken from GIT in previous task. Nothing else is done about file or its attributes in previous steps (previous tasks).

In the same time, running the same ./api/ using file-script task fails with "not executable" in build log. Prepending it with another INLINE-script task fixes the problem: 

chmod +x ./api/

Questions on the above:

1. How comes that "non-executable" script file runs just fine when started from the inline script?

2. Is it documented that file-script task can be useless without adding another inline task before? Shouldn't this important detail be added to "script task" help page?

3. Should the file-script task automatically set executable flag for the script file it is going to run (my vote here)?

4. Is there any global Bamboo configuration option to set executable flags for scripts or executive files taken from GIT?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events