Registry Auth Issues When Running Separate Pipeline Against Staging with QA_IMAGE and RELEASE
Problem
The Quality Engineering Tips and Tricks handbook page mentions that we can run a new pipeline with an MR's changes against staging by providing a RELEASE
and QA_IMAGE
variable using the values from the MR's e2e:package-and-test
pipeline:
It's also possible to trigger a manual GitLab-QA pipeline against a specific GitLab environment using the
RELEASE
andQA_IMAGE
variable from thepackage-and-test
job of GitLab's Merge Request. For example, here is the link to run a manual GitLab QA pipeline against Staging.
However, when following these steps, a pipeline is generated that requires manual actions, and a few issues occur when triggering these manually:
- The
cache-gitlab-qa
job's request toplay_manual.json
returns404
- Manually triggering the
sanity
stage fails withError response from daemon: Get "https://registry.gitlab.com/v2/": unauthorized: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/user/profile/account/two_factor_authentication#troubleshooting
Example pipeline: https://ops.gitlab.net/gitlab-org/quality/staging/-/pipelines/1750948
Proposal
Determine what are the new steps needed to run an MR's changes against staging and update the handbook