Exit script/build immediately upon error #1108
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this change, errors in the build process do not cancel the build, leading to additional errors that can obscure the cause of the build failure.
When I attempted to build planck locally lacking the
jar
command, the following happened:It appears that after
jar
was missing, acd
command didn't work and it took me to the root directory, where further commands attempted to read unrelated directories.With this change, the build errors immediately once
jar
fails:This seems like preferable behavior to me, but it might lead to issues if other commands depended on the
build
script to continue through some types of errors. I'm open to alternative approaches toset -e
.It's also worth considering whether such a setting should be in every bash script, if it's considered an improvement.