AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-09-16 12:00:08 +00:00
Code Issues Projects Releases Wiki Activity
main
gtk/.gitlab-ci
History
Benjamin Otte 504ca9c0c8 CI: run tests in a single dbus session 
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.
2024-08-24 18:36:23 +02:00
..
pages docs: Add a side bar to the docs.gtk.org landing page 2021-03-23 14:58:03 +00:00
.lock ci: Add a build with asan 2020-07-09 19:43:06 -04:00
clang-format-diff.py ci: Add a style check pass 2020-02-11 14:47:22 +00:00
fedora.Dockerfile ci: Fix a Vulkan problem in the F40 image 2024-08-08 14:19:25 -04:00
flatpak-build.sh Fix flatpak build 2024-04-22 16:18:58 +04:00
install-meson-project.sh ci: Use catch to capture stacktraces 2024-07-01 22:29:36 -04:00
meson-html-report.py ci: Handle deprecation warnings in report scripts 2023-11-25 11:21:48 -05:00
meson-junit-report.py ci: Handle deprecation warnings in report scripts 2023-11-25 11:21:48 -05:00
README.md ci: Update the Fedora image to Fedora 36 2022-05-14 12:23:02 -04:00
run-docker.sh ci: Make run-docker run work 2023-05-04 11:38:55 -04:00
run-single-test.sh Add a single test runner 2023-07-30 13:29:36 +03:00
run-style-check-diff.sh ci: Improve style check script 2022-09-09 19:41:42 -04:00
run-tests.sh CI: run tests in a single dbus session 2024-08-24 18:36:23 +02:00
show-info-linux.sh ci: Show OS release for our containers 2021-05-05 16:22:32 -04:00
show-info-macos.sh ci: Check for SDKROOT environment variable 2024-02-18 20:40:20 +01:00
test-docker.sh build: disable Vulkan by default 2021-07-20 14:00:25 -04:00
test-msvc.bat build: Enable Vulkan by default 2024-01-07 14:47:22 +01:00
test-msys2.sh build: Install vulkan-headers on msys CI 2024-03-28 21:09:44 +01:00

README.md

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, or latest

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}.Dockerfile file 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 using docker login or podman login
  • Update the image keys in the .gitlab-ci.yml file 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}.Dockerfile with the instructions to set up a build environment
  • Add the pip3 install meson incantation
  • 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.yml referencing 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:

  1. Build and upload fedora-base:$version+1
  2. Build and upload fedora:$version+1 based on fedora-base:version+1