From 31c69e188c6310d75d4b4be1a7663a5f0af2e83d Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A1n=20Tomko?= Date: Tue, 28 Jul 2020 11:05:16 +0200 Subject: [PATCH] ci: move sanity_checks after other stages MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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 Reviewed-by: Daniel P. Berrangé --- .gitlab-ci.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index c96e72198e..ee5a114e45 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,9 +2,9 @@ variables: GIT_DEPTH: 100 stages: - - sanity_checks - containers - builds + - sanity_checks .script_variables: &script_variables | export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)" @@ -481,6 +481,7 @@ potfile: # merge requests are submitted check-dco: stage: sanity_checks + needs: [] image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:master script: - /check-dco -- 2.47.2