2018-11-13 11:32:35 +01:00
|
|
|
|
# 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):
|
|
|
|
|
|
2022-12-30 21:18:47 +01:00
|
|
|
|
1. Edit `.gitlab-ci/*.Dockerfile` with the changes you want
|
2019-10-31 11:35:02 +01:00
|
|
|
|
1. Run `.gitlab-ci/run-docker.sh build --base=debian-stable --base-version=1` to
|
|
|
|
|
build the new image (bump the version from the latest listed for that `base`
|
2020-07-27 14:12:13 +02:00
|
|
|
|
on https://gitlab.gnome.org/GNOME/glib/container_registry). If rebuilding the
|
|
|
|
|
`coverity.Dockerfile` image, you’ll need to have access to [Coverity Scan][cs]
|
|
|
|
|
and will need to specify your project name and access token as the environment
|
|
|
|
|
variables `COVERITY_SCAN_PROJECT_NAME` and `COVERITY_SCAN_TOKEN`.
|
2019-10-31 11:35:02 +01:00
|
|
|
|
1. Run `.gitlab-ci/run-docker.sh push --base=debian-stable --base-version=1` to
|
|
|
|
|
upload the new image to the GNOME GitLab Docker registry
|
2018-11-13 11:32:35 +01:00
|
|
|
|
* 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][pat] and use that rather than
|
2020-05-14 17:26:12 +02:00
|
|
|
|
your normal password — the token should have `read_registry` and
|
|
|
|
|
`write_registry` permissions
|
2019-07-17 06:12:24 +02:00
|
|
|
|
1. Edit `.gitlab-ci.yml` (in the root of this repository) to use your new
|
2018-11-13 11:32:35 +01:00
|
|
|
|
image
|
|
|
|
|
|
2022-12-30 21:18:47 +01:00
|
|
|
|
[pat]: https://gitlab.gnome.org/-/profile/personal_access_tokens
|
2020-07-27 14:12:13 +02:00
|
|
|
|
[cs]: https://scan.coverity.com/
|