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?
I'm happy to announce that Bamboo 7.2 has been released and it’s overflowing with awesome new features. This will be the last major Server release before the launch of Bamboo DC. Bamboo logs We...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events