From ec272d8d4c5de1a143f3cec50e3f22d0f783f39b Mon Sep 17 00:00:00 2001 From: Anthony PERARD Date: Wed, 23 Aug 2023 16:23:34 +0100 Subject: [PATCH] CI: Always move the bisect build log back On failure of "build"-each-commit script, the next command that move the log back into the build directory isn't executed. Fix that by using "after_script" which is always executed even if the main "script" fails. (We would still miss the log when the jobs times out.) Signed-off-by: Anthony PERARD Acked-by: Andrew Cooper --- automation/gitlab-ci/test.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml index 8737f367c8..9aa8deabea 100644 --- a/automation/gitlab-ci/test.yaml +++ b/automation/gitlab-ci/test.yaml @@ -135,6 +135,7 @@ build-each-commit-gcc: CC: gcc script: - BASE=${BASE_SHA:-${CI_COMMIT_BEFORE_SHA}} TIP=${TIP_SHA:-${CI_COMMIT_SHA}} ./automation/gitlab-ci/build-each-commit.sh 2>&1 | tee ../build-each-commit-gcc.log + after_script: - mv ../build-each-commit-gcc.log . artifacts: paths: