Patch release pipeline: CNG images build verification
Context
During the patch release process, after tagging the releases, there are manual steps for the release managers to go check that the CNG images are successfully built.
Patch release issue tasks example
Check that the CNG Images are built. Do not play any manual jobs.
- 16.11.1: CNG builds
- 16.10.4: CNG builds
- 16.9.6: CNG builds
This issue is to automate the CNG image verification process by implementing jobs for the patch (security) release pipeline.
Proposal
- This check should be in the same stage as the tag
- There should be sufficient time in-between the EE and CE package verification and this verification job
- There should be an abstract logic that can be used for this from #20290
- Create announcement with the status of the pipeline in
#f_upcoming_release
- The job should retry max 3 times before failing
- The job should be retry-able
- Follow guidelines for the release pipelines in https://gitlab.com/gitlab-org/release-tools/-/blob/master/doc/release-pipelines.md
Exit Criteria
-
Release managers can rely on the the patch release pipeline to verify that CNG images are built successfully -
Announcement gets created in #f_upcoming_release
with the status of the completed build pipeline -
The release task issue is updated to use the patch release pipeline for the steps the pipeline automates
Edited by Jenny Kim