Draft: Cancel redundant pipelines with time partitioning
What does this MR do and why?
This is an alternative implementation of !137900 (closed) that differs by:
- We're using time range partition on pipeline creation date(for most of the time). Most of the records from the table are deleted when a non-interruptible job is started, but we'll keep at least one record for the last pipeline that is executed when merging the MR, so we need a different way of pruning old data and time range based partitioning offers this option.
- When a non-interruptible job is started we're deleting the tracking records by triggering events.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #423335 (closed)
Edited by Marius Bobin