2e13e8067c
We're currently building Gitaly images with three different Postgres versions. Ultimately though, Gitaly doesn't need Postgres installed in its images at all: the Postgres server is tied in as a service, and the only CI job that uses the the Postgres client is using a different image anyway. One part that had been using the Postgres client in the past was the logic to wait for Postgres to come up. But this has been migrated to instead rely on the health-checking logic provided by CI services in f89ffa3dc (ci: Stop waiting for Postgres manually, 2022-06-14) Stop installing Postgres in Gitaly images to reduce the number of images built. |
||
|---|---|---|
| .gitlab | ||
| assets | ||
| patches | ||
| scripts | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| Dockerfile.alpine-bash-jq-curl-git | ||
| Dockerfile.apollo | ||
| Dockerfile.build-git | ||
| Dockerfile.custom | ||
| Dockerfile.danger | ||
| Dockerfile.danger-ruby-2.6.6 | ||
| Dockerfile.gitlab-charts-build-base-helm-3.7 | ||
| Dockerfile.gitlab-helm3.5-kubectl1.17 | ||
| Dockerfile.gitlab-operator-build-base | ||
| Dockerfile.gitlab-puppeteer | ||
| Dockerfile.golangci-lint-alpine | ||
| Dockerfile.kaniko | ||
| Dockerfile.omnibus-gitlab-amazonlinux2 | ||
| Dockerfile.omnibus-gitlab-bionic | ||
| Dockerfile.omnibus-gitlab-bullseye | ||
| Dockerfile.omnibus-gitlab-buster | ||
| Dockerfile.omnibus-gitlab-centos7 | ||
| Dockerfile.omnibus-gitlab-centos8 | ||
| Dockerfile.omnibus-gitlab-cve-search | ||
| Dockerfile.omnibus-gitlab-depscan | ||
| Dockerfile.omnibus-gitlab-focal | ||
| Dockerfile.omnibus-gitlab-jessie | ||
| Dockerfile.omnibus-gitlab-opensuse15.1 | ||
| Dockerfile.omnibus-gitlab-opensuse15.2 | ||
| Dockerfile.omnibus-gitlab-opensuse15.3 | ||
| Dockerfile.omnibus-gitlab-stretch | ||
| Dockerfile.omnibus-gitlab-wheezy | ||
| Dockerfile.omnibus-gitlab-xenial | ||
| Dockerfile.release-tools | ||
| Dockerfile.sitespeed-gitlab | ||
| Dockerfile.terraform | ||
| Dockerfile.triage-ops-ruby-2.7 | ||
| Dockerfile.ubi-release | ||
| Dockerfile.www-gitlab-com-ruby-3.0-node-16 | ||
| LICENSE | ||
| README.md | ||
GitLab Build Images
This repository is used to build docker images that are used to build and test various parts of GitLab:
- Build Omnibus packages
- Test GitLab-CE/EE project
- Build gitlab-org/www-gitlab-com project
Adding a new image
There are two methods to adding a new image:
- Use a Dockerfile.
- Use a custom image with versioned features.
Use a Dockerfile
A bespoke image is one that uses it's own Dockerfile. In the interests of avoiding repetition, it's better to use the custom docker build if possible.
Assuming the image you want to add is called new-image:
- Add a test task:
new-image test: *test_build. - Add a new build task:
new-image: *build_and_deploy. - Add a Dockerfile:
Dockerfile.new-image.
Use a custom image with versioned features
To add a new image to the build, edit .gitlab-ci.yml.
With custom images, the name of the image is used to define the contents (as opposed to use a bespoke Dockerfile build).
For this reason, the name needs to be correctly defined.
The name is defined as [feature]-[version] pairs, separated by -.
Here are some example build names:
ruby-2.7-golang-1.15-git-2.29ruby-3.0.0-git-2.29-lfs-2.9-node-14.15-yarn-1.22-graphicsmagick-1.3.34ruby-3.0.0.patched-golang-1.14-git-2.29-lfs-2.9-chrome-87-node-14.15-yarn-1.22-postgresql-12-graphicsmagick-1.3.34
The first pair represents the base image and version. So ruby-3.0-... will use the ruby:3.0 base image, while
golang-1.15 will use the golang:1.15 base image.
Each of the following parts represents another feature and version. Available options are:
bazeliskchromedockergitgolanggraphicsmagicklfsnodepostgresqlrubyyarn
Adding a new build
As an example, if you want to add new image for Ruby 3.0 with git 2.29 and golang 1.15,
the name would be ruby-3.0-golang-1.15-git-2.29.
- Add a test task:
ruby-3.0-golang-1.15-git-2.29 test: *test_custom - Add a new build task:
ruby-3.0-golang-1.15-git-2.29 push: *build_and_deploy_custom
Note that the build name is also used for tagging the generated image, which means it cannot be longer than 128 characters.
Pushing a rebuild image
To build (or rebuild) a given image and push it, you need to enable manual action for a given job after it is merged to master.
By default we don't do it to ensure that an upstream dependency doesn't end up breaking our images unexpectedly. For reference, this happened in the past: https://gitlab.com/gitlab-org/gitlab/issues/205192
Note regarding Google Chrome
Google has a policy of yanking older versions of Google Chrome from their PPA
whenever a new major version is released. To help maintain consistent build
images, there is a CI step that saves the latest Google Chrome .deb into an the
GitLab package registry. The install for Chrome will attempt to retrieve from the
registry if it cannot find the file in the apt repository.
See scripts/cache-google-chrome for more details.
Contributing
See Contributing