Skip to content

[CI] add exit 0 to the end of CI scripts

Don Zickus requested to merge ci-fixups into os-build

Both of the CI scripts (ark-create-release and ark-update-configs) end on a conditional that is usually non-zero in the normal case. That leads that non-zero status to be the exit code of the overall script and thus tells gitlab that things failed when actually they passed.

ark-create-release.sh last line

test "$TO_PUSH" && eval "$PUSH_CMD" # TO_PUSH is off right now

ark-update-configs.sh last line

grep -q "remote:[ ]* WARNINGS" $TMPFILE && die "Server side warnings" ( normally there is no server side warnings)

Let's make sure the script returns success by adding an explicity 'exit 0' at the end.

Fixes: #123 (closed)

Signed-off-by: Don Zickus dzickus@redhat.com

Merge request reports