Anthony PERARD 21051291ad automation: Rework "build-each-commit-gcc" test ...

Current issues with this test are:
- when the job timeout, the log file is lost as there is no chance to
  run the `mv` command.
- GitLab job log is limited in size, so one usually have to download
  the artifacts, which may be missing.

Use $GITLAB_CI to detect when the script is run as part of a GitLab
pipeline. GitLab will add "GITLAB_CI=true" in the environment
variables.

When run as part of $GITLAB_CI, ignore "dirty" worktree to allow to
write "build-each-commit-gcc.log", which can then be grabbed as
artifacts, even when the job timeout. The `git clean` command is
changed to keep those build logs.

When run as part of $GITLAB_CI, we will also store the build output in
a log file instead of writing it to stdout, because GitLab's job log
is limited. But we will write the log to stdout in case of error, so
we can find out more quickly why there's been an error.

This patch also make use of a GitLab feature, "log sections", which we
will collapse by default. One section per commit been built.

There's a bit of colour added to the logs.

Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>

2024-02-26 16:05:59 +01:00

..

analyze.yaml

automation/eclair: improve scheduled analyses

2023-11-30 18:59:30 -08:00

build-each-commit.sh

automation: Rework "build-each-commit-gcc" test

2024-02-26 16:05:59 +01:00

build.yaml

automation: Switch yocto-qemux86-64 job to run on x86

2024-02-06 16:47:04 -08:00

test.yaml

automation: Rework "build-each-commit-gcc" test

2024-02-26 16:05:59 +01:00