ci: move sanity_checks after other stages

Be less hostile to developers and run the build jobs even
if the dco-check failed. That way they can test their own
"private" branches without a sign-off.

Also specify empty `needs` for it, since it does not depend
on any of the jobs in the container phase and can be run
right away.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Ján Tomko 2020-07-28 11:05:16 +02:00
parent 00bb850eb0
commit 31c69e188c

View File

@ -2,9 +2,9 @@ variables:
GIT_DEPTH: 100 GIT_DEPTH: 100
stages: stages:
- sanity_checks
- containers - containers
- builds - builds
- sanity_checks
.script_variables: &script_variables | .script_variables: &script_variables |
export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)" export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"
@ -481,6 +481,7 @@ potfile:
# merge requests are submitted # merge requests are submitted
check-dco: check-dco:
stage: sanity_checks stage: sanity_checks
needs: []
image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:master image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:master
script: script:
- /check-dco - /check-dco