Skip to content

Set "gitlab_canary=false" cookie in Staging pipeline

Nailia Iskhakova requested to merge qe-always-disable-canary-for-staging into master

Directly set QA_COOKIES: "gitlab_canary=false" to Staging (gstg) pipelines configs to ensure that pipelines are not running against Staging Canary.

According to https://about.gitlab.com/handbook/engineering/infrastructure/environments/canary-stage/#accessing-the-canary-stage-of-an-environment

5% of traffic for the "main" stage is automatically instead sent to the "canary" stage of an environment if the gitlab_canary is not set which is the default for most users. If you wish to ensure your requests are never sent to canary, manually set the gitlab_canary cookie to false in whatever browser/tool you are using to talk to the environment or ensure that "current" is toggled on https://next.gitlab.com

The change should resolve issues like gitlab-org/gitlab#422664 (comment 1520973341) when Staging pipeline was using SHA from Staging Canary

Related to:

Merge request reports