mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2025-01-11 13:10:07 +00:00
504ca9c0c8
Instead of every test spawning their own dbus, make the tests share the same server, just like they share their own compositor. This should speed up things a bit and avoid weird interactions when multiple dbus processes exist. |
||
|---|---|---|
| .. | ||
| pages | ||
| .lock | ||
| clang-format-diff.py | ||
| fedora.Dockerfile | ||
| flatpak-build.sh | ||
| install-meson-project.sh | ||
| meson-html-report.py | ||
| meson-junit-report.py | ||
| README.md | ||
| run-docker.sh | ||
| run-single-test.sh | ||
| run-style-check-diff.sh | ||
| run-tests.sh | ||
| show-info-linux.sh | ||
| show-info-macos.sh | ||
| test-docker.sh | ||
| test-msvc.bat | ||
| test-msys2.sh | ||
GTK CI infrastructure
GTK uses different CI images depending on platform and jobs.
The CI images are Docker containers, generated either using docker or
podman, and pushed to the GitLab container registry.
Each Docker image has a tag composed of two parts:
${image}: the base image for a given platform, like "fedora" or "debian-stable"${number}: an incremental version number, orlatest
See the container registry for the available images for each branch, as well as their available versions.
Note that using latest as version number will overwrite the most
recently uploaded image in the registry.
Checklist for Updating a CI image
- Update the
${image}.Dockerfilefile with the dependencies - Run
./run-docker.sh build --base ${image} --version ${number} - Run
./run-docker.sh push --base ${image} --version ${number}once the Docker image is built; you may need to log in by usingdocker loginorpodman login - Update the
imagekeys in the.gitlab-ci.ymlfile with the new image tag - Open a merge request with your changes and let it run
Checklist for Adding a new CI image
- Write a new
${image}.Dockerfilewith the instructions to set up a build environment - Add the
pip3 install mesonincantation - Run
./run-docker.sh build --base ${image} --version ${number} - Run
./run-docker.sh push --base ${image} --version ${number} - Add the new job to
.gitlab-ci.ymlreferencing the image - Open a merge request with your changes and let it run
Checklist for Adding a new dependency to a CI image
Our images are layered, and the base (called fedora-base) contains all the rpm payload. Therefore, adding a new dependency is a 2-step process:
- Build and upload fedora-base:$version+1
- Build and upload fedora:$version+1 based on fedora-base:version+1