[PATCH 1/2] CI: always put the build logs in an artifact

[PATCH 1/2] CI: always put the build logs in an artifact

[ross.burton]

From: Ross Burton <ross.burton@arm.com>

It's useful to have known good logs when debugging problems, so always
preserve the logs.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 74105e65..f700ee0f 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -64,7 +64,7 @@ stages:
     - ./ci/check-warnings $KAS_WORK_DIR/build/warnings.log
   artifacts:
     name: "logs"
-    when: on_failure
+    when: always
     paths:
       - $CI_PROJECT_DIR/work/build/tmp/work*/**/temp/log.do_*.*
       - $CI_PROJECT_DIR/work/build/tmp/work*/**/testimage/*
-- 
2.34.1

[PATCH 2/2] CI: print the name of the documentation when building

[ross.burton]

From: Ross Burton <ross.burton@arm.com>

Make it clear what documentation tree is being built.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 .gitlab-ci.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index f700ee0f..b2246743 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -282,6 +282,7 @@ documentation:
     - |
       sudo pip3 install -r meta-arm-bsp/documentation/requirements.txt
       for CONF in meta-*/documentation/*/conf.py ; do
+        echo Building $CONF...
         SOURCE_DIR=$(dirname $CONF)
         MACHINE=$(basename $SOURCE_DIR)
         sphinx-build -vW $SOURCE_DIR build-docs/$MACHINE
-- 
2.34.1

Re: [PATCH 1/2] CI: always put the build logs in an artifact

[Jon Mason]

On Wed, 21 Jun 2023 15:36:09 +0100, ross.burton@arm.com wrote:
> It's useful to have known good logs when debugging problems, so always
> preserve the logs.

Applied, thanks!

[1/2] CI: always put the build logs in an artifact
      commit: 60abe46474060064f1080513f76a0e333ca487df
[2/2] CI: print the name of the documentation when building
      commit: 782ea3cd1688a14b4ad065bf47b1f9d8d0ea3fa4

Best regards,
-- 
Jon Mason <jon.mason@arm.com>