Skip to content

Trigger deploys to release-environments on stable branches

Graeme Gillies requested to merge ggillies/add-deploys-release-environments into master

What does this MR do and why?

Trigger deploys to release-environments on stable branches

Part of gitlab-com/gl-infra/delivery#2696 (closed)

This change expands upon the start-release-environments child pipeline to do the following

  • Correct how we tag images built in cng-mirror by leveraging the IMAGE_TAG_EXT field to uniquely tag images. Some examples of this working are at

https://gitlab.com/gitlab-org/build/CNG-mirror/-/jobs/4090399906 for 15-9-stable

https://gitlab.com/gitlab-org/build/CNG-mirror/-/jobs/4090296623 for 15-10-stable

  • Adds a new stage to actually do a downstream pipeline trigger to the release-environments repository in order to actually trigger a deploy. This passes in the environment to deploy to and a json object which is the versions of each component to deploy. The work for the release-environments repository to support this was done in https://gitlab.com/gitlab-com/gl-infra/release-environments/-/merge_requests/51

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

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.

Merge request reports