.ostc-ci: sprinkle ample quantity of "set -ex"
It seems that GitLab CI is not running with
set -e but a weaker
equivalent, as evidently proven by the recent discovery of incorrect
shell syntax going unnoticed.
While unconfirmed it seems that what is going on is that each of the
after_script sections being combined
into lists and executed in distinct processes, one by one. A simple
command, such as
false, reports its status through the exit code of
bash. Compound commands that run multiple processes as a single element
of the various script sections, can have internal failures without
immediately stopping execution.
To shed some light, add
set -ex in all the jobs that don't already
inherit it with the job extension mechanism.
Signed-off-by: Zygmunt Krynicki email@example.com Change-Id: If41b71e5cca3c58d1c6ed163fb9bd147c2d14481