6f34b404e8
Passing a version number of NetworkManager to this new script, it prints what distros are using that NM version and generates a new content for .gitlab-ci/config.yml. Automatically generating the config.yml content is useful because we can easily update what distros we test in the CI and the Tier that they belong, depending on what version of NM do they ship and whether they have reached EOL or not. Important: when generating a config.yml for an stable branch, not for main, it must be generated from main. This is because we are not going to keep distros-info.yml up to date in all branches, only in main. |
||
|---|---|---|
| .. | ||
| alpine-install.sh | ||
| ci.template | ||
| config.yml | ||
| coverity.sh | ||
| debian-install.sh | ||
| distros-info.yml | ||
| distros_support.py | ||
| 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.