This repository has been archived by the owner on Jun 16, 2024. It is now read-only.
prepare.sh: use errtrace to trigger trap from function #9
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.
When using -e/-o errexit without the -E/-o errtrace option, trap won't
be triggered if a command fails inside a function. In this case, all
relevant commands are executed inside start_container() and
install_dependencies() functions.
When the error is properly propagated, the trap error handling actually
works and the gitlab runner will attempt to re-try to start-up the
container since it correctly detects that the job failed during the
preparation stage.
See https://stackoverflow.com/a/35800451 for more details about -e -E
interaction