5a6c8c9ba4
- after modifying .gitlab-ci, the template must be regenerated by
running `ci-fairy generate-template`
- when swapping tier1 from f38 to f39, the list in tier2 must be updated
too.
Fixes: e2f04f0d2cc3 ('device: fix generated 'wifi.cloned-mac-address="stable-ssid"' for stable-id')
|
||
|---|---|---|
| .. | ||
| alpine-install.sh | ||
| ci.template | ||
| config.yml | ||
| debian-install.sh | ||
| 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.