Skip to content

Add a task to check if all MRs are merged in patch release

What does this MR do and why?

Describe in detail what your merge request does and why.

Content

  • Add a task to check if all MRs are merged in patch release

Quote from gitlab-com/gl-infra/delivery#20419 (closed):

The current procedure only check if all commits in security/gitlab is deployed to .com (via auto-deploy). It has a hole: MWPS MRs are not merged. I think the idea is that after setting MWPS, there are lots of time between the two days for the pipelines to finish and the MRs are merged. However, it is not always the case. The pipeline can fail because of various reasons, not to say the merge action sometimes also fails with an unknown reason (e.g. An error occurred while merging. Try again. ). We are lucky that this is caught when merging the MRs targeting the stable branches. However, it already costs us a lot of time since we need to rerun the PDM and the security_release_release_preparation:start job.

Ref: gitlab-com/gl-infra/delivery#20419 (closed)

Edited by Dat Tang

Merge request reports

Loading