mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-11-10 11:26:16 +01:00
5370df540c
This is a departure from our policy of using the minimum required Meson version, but I think it might be worth a try to see if it fixes the persistent intermittent build failures on these platforms due to what looks like build dependency graph issues. For example: - https://gitlab.gnome.org/GNOME/glib/-/jobs/2579411 - https://gitlab.gnome.org/GNOME/glib/-/jobs/2578792 - https://gitlab.gnome.org/GNOME/glib/-/jobs/2579220 - https://gitlab.gnome.org/pwithnall/glib/-/jobs/2588507 I was looking at trying to diagnose some of these failures in order to potentially file bugs against Meson, but the first step is really to test against the latest version of Meson. So here we are. Crucially, our other CI jobs continue to use the minimum Meson version required by GLib, so we continue to test that GLib builds with its minimum dependencies. I do not plan to change that. Also crucially, this MR continues to use a specific Meson version, rather than asking `pip` to install the latest available. Doing that could lead to unexpected regressions in future, and that’s not what GLib’s CI is meant to be testing for. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> |
||
---|---|---|
.. | ||
android-ndk.sh | ||
cache-subprojects.sh | ||
check-missing-install-tag.py | ||
check-todos.py | ||
clang-format-diff.py | ||
coverage-docker.sh | ||
coverity-model.c | ||
coverity.Dockerfile | ||
cross_file_android_arm64_31.txt | ||
cross_file_ios_example.txt | ||
cross_file_mingw64.txt | ||
debian-stable.Dockerfile | ||
fedora.Dockerfile | ||
fixup-cov-paths.py | ||
install-gitlab-cobertura-tools.sh | ||
mingw.Dockerfile | ||
README.md | ||
run-black.sh | ||
run-check-todos.sh | ||
run-docker.sh | ||
run-flake8.sh | ||
run-reuse.sh | ||
run-shellcheck.sh | ||
run-style-check-diff.sh | ||
run-tests.sh | ||
search-common-ancestor.sh | ||
show-execution-environment.sh | ||
test-msvc.bat | ||
test-msys2.sh |
CI support stuff
Docker image
GitLab CI jobs run in a Docker image, defined here. To update that image (perhaps to install some more packages):
- Edit
.gitlab-ci/*.Dockerfile
with the changes you want - Run
.gitlab-ci/run-docker.sh build --base=debian-stable --base-version=1
to build the new image (bump the version from the latest listed for thatbase
on https://gitlab.gnome.org/GNOME/glib/container_registry). If rebuilding thecoverity.Dockerfile
image, you’ll need to have access to Coverity Scan and will need to specify your project name and access token as the environment variablesCOVERITY_SCAN_PROJECT_NAME
andCOVERITY_SCAN_TOKEN
. - Run
.gitlab-ci/run-docker.sh push --base=debian-stable --base-version=1
to upload the new image to the GNOME GitLab Docker registry- If this is the first time you're doing this, you'll need to log into the registry
- If you use 2-factor authentication on your GNOME GitLab account, you'll
need to create a personal access token and use that rather than
your normal password — the token should have
read_registry
andwrite_registry
permissions
- Edit
.gitlab-ci.yml
(in the root of this repository) to use your new image