matteo
/
malcontent
1
0
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Wiki Activity
malcontent/.gitlab-ci
History
Philip Withnall e6f82a4a86 ci: Use pre-built Docker images for CI builds 
Rather than updating the packages on a generic Debian Unstable image
every time a CI build happens, pre-build the image and pre-download all
the dependencies.

This should speed the CI runs up; they currently take about 4 minutes.

Signed-off-by: Philip Withnall <withnall@endlessm.com>
 		2020-07-21 11:58:51 +01:00
..
README.md ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
cache-subprojects.sh ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
coverage-docker.sh ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
debian-unstable.Dockerfile ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
lcovrc ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +01:00
meson-junit-report.py ci: Use pre-built Docker images for CI builds 2020-07-21 11:58:51 +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