Protection for CI jobs triggered by mistake (gitlab bugs)
Currently the CI job scripts depend on the correct triggering of the jobs by the logic coded into the gitlab-ci.yml
file.
If a job gets triggered by mistake it will return a failure, because the grep
commands will not find any matching file. In principle there is no need for such a triggered job to return failure.
This can be solved by using
set -e
grep ...
set +e