Hi Alex, On 21/5/24 14:53, Alex Bennée wrote:
There are a few more bits referencing centos8 in the tree which needed cleaning up. After this we can remove the dedicated runner from the gitlab registration. If we want to keep a dedicated Centos runner then we can add back the bits needed to set it up (although arguably we could have a single build-environment setup that handles all distros and integrates with lcitool).
Do you you mean we should generate scripts/ci/setup/build-environment.yml with lcitool?
Otherwise should we update it?
Alex. Alex Bennée (4): ci: remove centos-steam-8 customer runner docs/devel: update references to centos to later version tests/vm: update centos.aarch64 image to 9 tests/vm: remove plain centos image docs/devel/ci-jobs.rst.inc | 7 - docs/devel/testing.rst | 8 +- .gitlab-ci.d/custom-runners.yml | 1 - .../custom-runners/centos-stream-8-x86_64.yml | 24 --- .../org.centos/stream/8/build-environment.yml | 82 -------- .../ci/org.centos/stream/8/x86_64/configure | 198 ------------------ .../org.centos/stream/8/x86_64/test-avocado | 65 ------ scripts/ci/org.centos/stream/README | 17 -- tests/vm/Makefile.include | 1 - tests/vm/centos | 51 ----- tests/vm/centos.aarch64 | 10 +- 11 files changed, 9 insertions(+), 455 deletions(-) delete mode 100644 .gitlab-ci.d/custom-runners/centos-stream-8-x86_64.yml delete mode 100644 scripts/ci/org.centos/stream/8/build-environment.yml delete mode 100755 scripts/ci/org.centos/stream/8/x86_64/configure delete mode 100755 scripts/ci/org.centos/stream/8/x86_64/test-avocado delete mode 100644 scripts/ci/org.centos/stream/README delete mode 100755 tests/vm/centos
