AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-12-27 06:00:22 +00:00
Code Issues Projects Releases Wiki Activity
3eca28e4b5
gtk/.gitlab-ci
History
Emmanuele Bassi f25beff7a6 docs: Restructure the list of UI libraries 
Put GTK at the top.
2021-03-19 17:23:46 +00:00
..
pages docs: Restructure the list of UI libraries 2021-03-19 17:23:46 +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-base.Dockerfile ci: Update the Fedora image to F33 2021-02-11 22:02:39 -05:00
fedora-docs.Dockerfile ci: Update the fedora-docs Docker image 2021-03-11 16:37:29 +00:00
fedora.Dockerfile ci: Update the Fedora image to F33 2021-02-11 22:02:39 -05:00
flatpak-build.sh ci: publish demo apps to the Nightly repository 2020-11-13 20:38:09 +02:00
meson-html-report.py ci: Add the backend to the reports 2020-05-15 19:49:18 -04:00
meson-junit-report.py ci: Add the backend to the reports 2020-05-15 19:49:18 -04:00
README.md Rename base version argument in run-docker.sh 2021-03-11 16:37:29 +00:00
run-docker.sh Rename base version argument in run-docker.sh 2021-03-11 16:37:29 +00:00
run-style-check-diff.sh ci: Create new origin for forks 2020-06-29 13:14:40 +01:00
run-tests.sh ci: Don't print lsan suppressions 2021-01-22 13:01:09 -05:00
show-execution-environment.sh ci: Add a macos build 2021-01-03 21:34:04 -05:00
test-docker.sh ci: Build with profiler support 2020-01-21 18:20:05 -05:00
test-msys2.sh CI: Enable introspection again for the Windows build 2020-10-01 15:16:18 +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.

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