AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
adc7bf9f25
gtk2/.gitlab-ci
History
Emmanuele Bassi adc7bf9f25 ci: Put the branch name in the HTML header
2020-02-13 14:55:39 +00:00
..
clang-format-diff.py ci: Add a style check pass 2020-02-11 14:47:22 +00:00
fedora.Dockerfile ci: Add a style check pass 2020-02-11 14:47:22 +00:00
flatpak-build.sh ci: Update flatpak job 2020-02-12 18:24:54 +00:00
meson-html-report.py ci: Put the branch name in the HTML header 2020-02-13 14:55:39 +00:00
meson-junit-report.py Add licensing and copyright notice to report generators 2019-04-16 11:43:23 +01:00
README.md ci: Replicate the CI image scripts from GLib 2020-02-11 13:39:52 +00:00
run-docker.sh ci: Replicate the CI image scripts from GLib 2020-02-11 13:39:52 +00:00
run-style-check-diff.sh ci: Add a style check pass 2020-02-11 14:47:22 +00:00
run-tests.sh ci: Fix linking of the CI assets in the report 2020-02-12 18:12:53 +00:00
test-docker.sh ci: Build with profiler support 2020-01-21 18:20:05 -05:00
test-msys2.sh CI: Install a newer MSYS2 pango package; Don't allow failures again 2019-12-18 09:25:06 +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.

Checklist for Updating a CI image

  • Update the ${image}.Dockerfile file with the dependencies
  • Run ./run-docker.sh build --base ${image} --base-version ${number}
  • Run ./run-docker.sh push --base ${image} --base-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} --base-version ${number}
  • Run ./run-docker.sh push --base ${image} --base-version ${number}
  • Add the new job to .gitlab-ci.yml referencing the image
  • Open a merge request with your changes and let it run