Useful to have easily accessible the info of all the distros that we test, including the version of NM that they ship and their EOL dates so we can know when to stop testing them. For now this is only informative, but we can use this info, for example, to generate the `.gitlab-ci/config.yml` file automatically for each stable branch. |
||
|---|---|---|
| .. | ||
| alpine-install.sh | ||
| ci.template | ||
| config.yml | ||
| coverity.sh | ||
| debian-install.sh | ||
| distros-info.yml | ||
| fedora-install.sh | ||
| README.md | ||
| run-test.sh | ||
.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:
- run
tools/check-gitlab-ci.sh - run
make check-local-gitlab-ci, which runs 1). This also runs as part ofmake 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.