AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
main
gtk2/.gitlab-ci
History
Matthias Clasen 1cee54009a ci: Disable the testsuite in flatpak builds 
No need to build the testsuite when we are
just producing flatpaks.
2023-03-05 07:26:17 -08: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
fedora.Dockerfile ci: Update image 2023-02-17 12:24:09 +00:00
flatpak-build.sh ci: Disable the testsuite in flatpak builds 2023-03-05 07:26:17 -08:00
meson-html-report.py CI: Include reftest nodes in artifacts 2022-05-18 19:54:34 +02:00
meson-junit-report.py Update references to master in the repository 2021-11-29 17:37:49 -05:00
README.md ci: Update the Fedora image to Fedora 36 2022-05-14 12:23:02 -04:00
run-docker.sh ci: Add no-cache option to run-docker.sh script 2023-02-17 12:24:09 +00:00
run-style-check-diff.sh ci: Improve style check script 2022-09-09 19:41:42 -04:00
run-tests.sh ci: More verbose output from asan 2022-12-20 00:32:51 -05:00
show-info-linux.sh ci: Show OS release for our containers 2021-05-05 16:22:32 -04:00
show-info-osx.sh ci: Show OS release for our containers 2021-05-05 16:22:32 -04:00
test-docker.sh build: disable Vulkan by default 2021-07-20 14:00:25 -04:00
test-msvc.bat ci: Update meson version used for vs2017 job 2022-12-19 03:09:11 +05:30
test-msys2.sh CI: remove workaround for some subproject builds failing on Windows 2022-08-04 22:26:04 +02: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