69efb4660c
This will force to regenerate the various images of the distributions that we want to test so we get an updated snapshot on them. Otherwise we might be testing a months old version of them. A bug in ci-fairy was making the deletion of the images to partially fail. It is fixed in the latest version of ci-fairy, so we need to update the value of templates_sha to pick it. The task will run only on pipelines of type "scheduled". Then we can create a weekly scheduled pipeline in Gitlab. |
||
|---|---|---|
| .. | ||
| 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.