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 <anthony.perard@citrix.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Anthony PERARD authored and Andrew Cooper committed 2023-08-24 19:55:08 +01:00
1 parent 0742b0a081
commit ec272d8d4c
1 file changed
+1
+1
View File
@@ -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:
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.