Skip to content

Ownership of runner manager machine used for QA jobs

Status update:

  1. Decided to move the runner manager used for gitlab-qa runs in package-and-build pipelines to a folder owned by Quality
  2. A new GCP project named gitlab-qa-runners was created for this purpose
  3. Will create a new VM in this project and get gitlab-runner installed in it. Auto-scaled VMs using docker-machine will also be created in this project.

QA jobs that require higher computing power (anchor high_capacity in .gitlab-ci.yml file) are managed by the runner build-trigger-runner-manager-gitlab-org. This was setup when QA jobs from CE, EE and omnibus-gitlab jobs were run in the omnibus-gitlab pipeline. However, that situation have now changed and the jobs are now running in the QA pipeline itself, and are just triggered from omnibus-gitlab pipeline after package and docker jobs.

The ownership/maintenance of this runner manager was initially with Distribution team. Since now it is being used by only QA pipelines, I think it is right to hand over the ownership to Quality team.

WDYT @marin @meks @grzesiek @rymai ?

PS: For completeness, here are some additional info

  1. QA jobs that doesn't required higher computing power are handled by shared auto-scaling runners.
  2. Package build and Docker build jobs that are part of triggered pipeline in omnibus-gitlab are managed by another runner - build-trigger-runners-manager-gcp triggered-builds-runner-manager-gcp

For reference:

Edited by Balasankar 'Balu' C