NetworkManager/.gitlab-ci
Íñigo Huguet e8532d4a41 CI: add testlog.txt as build artifacts
That way we will be able to check the logs in the case of failure.

(cherry picked from commit 0d4c8a235a)
(cherry picked from commit b6e2533f82)
(cherry picked from commit fc238062bd)
2024-12-24 16:37:54 +01:00
..
alpine-install.sh gitlab-ci: enable test build on alpine linux 2020-12-11 18:14:10 +01:00
ci.template CI: add testlog.txt as build artifacts 2024-12-24 16:37:54 +01:00
config.yml ci: run with distros that uses the current version 2024-06-28 11:14:22 +00:00
debian-install.sh gitlab-ci: fix detection and handling of Ubuntu 18.04 2023-06-30 18:51:13 +02:00
fedora-install.sh gitlab-ci: drop builds for CentOS 8 (8.1.1911, 8.2.2004, 8.3.2011) 2023-11-15 10:52:53 +01:00
README.md gitlab-ci: add .gitlab-ci/README.md 2023-06-06 12:35:09 +02:00
run-test.sh CI: add testlog.txt as build artifacts 2024-12-24 16:37:54 +01:00

.gitlab-ci

We run tests in the gitlab-ci pipeline at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/pipelines

This directory contains a template for generating .gitlab-ci.yml.

It uses ci-templates project.

To get the right version of ci-templates, see the "Regenerate with" comment in .gitlab-ci.yml. It shows how to install ci-fairy via python pip. The exact version to be used is hard-coded as .templates_sha variable in ci.template file.

Whenever changing relevant files, .gitlab-ci.yml must be regenerated. Regenerate the yml by running ci-fairy generate-template.

There are also tests for checking that the yml is correct:

  1. run tools/check-gitlab-ci.sh
  2. run make check-local-gitlab-ci, which runs 1). This also runs as part of make check.

In both cases, the test is skipped if ci-fairy is not in the path. Install the correct ci-fairy version.

In gitlab-ci pipeline, the "check-tree" test also checks that .gitlab-ci.yml is up to date.