[go: up one dir, main page]

Adding capabitity to run tests on images from custom registry

What does this MR do and why?

I am currently working on a private GitLab fork project which also uses a private fork of omnibus-gitlab-mirror repository to build images. The orchestrated tests in the MR pipelines are all failing, as gitlab-qa is unable to access the container registry of the private Gitlab fork project as well as the private omnibus-gitlab-mirror project.

This MR adds capability for the user to pass in custom registry url as well as credrentials for gitlab-qa to pull images from private project registries.

The new environment variables introduced are GITLAB_CUSTOM_ACCESS_TOKEN , GITLAB_CUSTOM_USERNAME and QA_CUSTOM_REGISTRY.

Tested by passing custom parameters : https://gitlab.com/gitlab-org/gitlab-qa/-/pipelines/1551531378

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Vishal Patel

Merge request reports

Loading