Migrate to shared Runner fleet from gitlab-runner-builder
Overview
At the moment for us to build/publish Docker images, we have a specific Runner called gitlab-runner-builder.gitlap.com
which is tagged by the release
tag. Whilst working on #2076 (closed) we found out that the Kernel version is not over the required >= 4.8 version.
The only thing different that gitlab-runner-build.gitlap.com
has over the shared Runners is that it has environments
set with values that can be used to publish to packagecloud
, s3
, docker hub
.
Below is the environment keys that we use:
PACKAGECLOUD_TOKEN
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
DOCKER_HUB_USER
DOCKER_HUB_PASSWORD
Proposal
-
Migrate the variables into CI variables in Settings > CI/CD > Variables setting the following
-
PACKAGECLOUD_TOKEN
set as protected since it's only needed for master, stable branches and tags which are protected. -
AWS_ACCESS_KEY_ID
available all the time since we need it to push to s3 for development branches as well. -
AWS_SECRET_ACCESS_KEY
available all the time since we need it to push to s3 for development branches as well. -
DOCKER_HUB_USER
set as protected since it's only needed for master, stable branches and tags which are protected. -
DOCKER_HUB_PASSWORD
set as protected since it's only needed for master, stable branches and tags which are protected.
All variables should be masked if possible
-
-
Remove the
release
tag from the.gitlab/ci/release.gitlab-ci.yml
so shared Runners are used. -
Remove
gitlab-runner-build.gitlap.com
from the project-specific Runners👉 #21299 (comment 310291084)
The rest should probably be moved to the infra issue tracker:
- Remove anything related to
gitlab-runner-build.gitlap.com
fromchef-repo
such as:nodes/gitlab-runner-builder.gitlap.com.json
roles/gitlab-runner-builder.json
- Any data bags related to it
- Remove it from runbook
- Remove the machine from the hosting provider (Digitalocean?)
- Remove it from Prometheus