67eb8c5c2b
The test "tarball+meson" fails on systems with old meson version with
the message "ERROR: Neither directory contains a build file
meson.build". This message is raised when calling `meson dist` from the
build directory.
According to meson documentation, `meson dist` is supported since 0.52,
and older vesions need to execute `ninja dist`.
https://mesonbuild.com/Creating-releases.html
Also, when using meson.add_dist_script, the env variable MESON_SOURCE_ROOT
is not passed in versions < 0.54. As we don't use it in the script,
don't assert for it.
We claim to support down to meson 0.47.3 (we need to raise it because we
are actually using a bit newer features, but that's another topic). Use
`ninja dist` that will work fine on old and new meson.
Fixes:
|
||
---|---|---|
.. | ||
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.