Move release-environments child pipeline to be sourced from master
What does this MR do and why?
Part of gitlab-com/gl-infra/delivery#19905 (closed)
In order to make development of release-environments easier by reducing backports and skew of code across stable branches, we want to make it so regardless of GitLab version being deployed to a release-environment, we are always using the child-pipeline setup from master.
This means we can can make changes to the pipeline setup on master
,
and it will take effect across all stable branches.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
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.
-
I have evaluated the MR acceptance checklist for this MR.