Patch release pipeline: check-packages verification after publish stage
Context
During the patch release process, after security_release_publish
stage of the patch (security) release pipeline is started, the release managers manually verify that the check-packages
job completed successfully on dev omnibus-gitlab
stable branches
Patch release issue tasks example
Verify that the check-packages
job completes:
EE check-packages
on 16.11.1+ee.0CE check-packages
on 16.11.1+ce.0EE check-packages
on 16.10.4+ee.0CE check-packages
on 16.10.4+ce.0EE check-packages
on 16.9.6+ee.0CE check-packages
on 16.9.6+ce.0
This issue is to automate this verification process by implementing a job for the patch (security) release pipeline.
Proposal
- This check should be at the end of
security_release_publish
stage, similar to how the release task issue is currently organized. - The url on the release task issue currently points to the stable branches, but we need to drill down to the pipeline for the latest commit to get its status for one of its jobs
check-packages
. - 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 perform this check -
The release task issue is updated to use the patch release pipeline for the steps the pipeline automates
Edited by Jenny Kim