You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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/myfilescript.sh "$@"
The above works fine. The /api/myfilescript.sh script file that it starts is taken from GIT in previous task. Nothing else is done about myfilescript.sh file or its attributes in previous steps (previous tasks).
In the same time, running the same ./api/myfilescript.sh using file-script task fails with "not executable" in build log. Prepending it with another INLINE-script task fixes the problem:
chmod +x ./api/myfilescript.sh
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?