Run the script using bash
Another option would be to run the script using bash, this would omit the need to modify the files' permissions.
bash path/to/file.sh
Alternatively:
sh path/to/file.sh
Note that
In this case you're not executing the script itself, you're executing bash
or sh
which then runs the script. Therefore the script does not need to be executable.
Make sense?
I've found this solution incredibly useful myself. I'm mainly running node
& npm
projects on travis-ci, those builds make use of the npm test
command which you can configure to be anything.
I'm order to modify file permission I need to use sudo chmod ...
on my local machine. But you can't always use sudo
on travis-ci.
sh file.sh
allows me to run my tests both locally and on travis-ci without having to manually update permissions.
chmod ugo+x
rather thana+x
. (No idea if there are cases where this matters!) – Tertias