Destroy pipelines before destroying merge requests
What does this MR do and why?
Destroys the pipelines before destroying the merge request because by default it is using LFK which constructs database queries to delete the data and leaves orphaned artifact files in the object storage.
Related to #565940 (closed)
References
Screenshots or screen recordings
Query examples for a merge request with more than 500 pipelines:
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131717
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131718
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131719
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131720
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131721
- https://postgres.ai/console/gitlab/gitlab-production-ci/sessions/43089/commands/131722
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #565940 (closed)
Edited by Marius Bobin