matteo
/
malcontent
1
0
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Wiki Activity
malcontent/.gitlab-ci
History
Georges Basile Stavracas Neto c31640fa12 build: Switch to GTK4 and libadwaita 
Switch the build system to GTK4 and libadwaita, instead of GTK3
and libhandy.

This commit breaks the build.
 		2022-07-20 19:23:12 -03:00
..
README.md ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
cache-subprojects.sh ci: Limit depth of clone of subprojects 2021-03-22 17:54:42 +00:00
coverage-docker.sh ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
debian-unstable.Dockerfile build: Switch to GTK4 and libadwaita 2022-07-20 19:23:12 -03:00
lcovrc ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
meson-junit-report.py ci: Rename master to main branch 2021-09-17 12:39:17 +01:00
run-docker.sh ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
run-tests.sh ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00

README.md

CI support stuff

Docker image

GitLab CI jobs run in a Docker image, defined here. To update that image (perhaps to install some more packages):

  1. Edit .gitlab-ci/Dockerfile with the changes you want
  2. Run .gitlab-ci/run-docker.sh build --base=debian-unstable --base-version=1 to build the new image (bump the version from the latest listed for that base on https://gitlab.freedesktop.org/pwithnall/malcontent/container_registry)
  3. Run .gitlab-ci/run-docker.sh push --base=debian-unstable --base-version=1 to upload the new image to the GNOME GitLab Docker registry
    • If this is the first time you're doing this, you'll need to log into the registry
    • If you use 2-factor authentication on your GNOME GitLab account, you'll need to create a personal access token and use that rather than your normal password — the token should have read_registry and write_registry permissions
  4. Edit .gitlab-ci.yml (in the root of this repository) to use your new image