Pipeline retention policies can't be extended for protected or default branches
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The Problem
Our current pipeline retention policy configuration isn't very flexible. When we talk about configuration a retention policy, it's just age of the Pipeline. There's also the possibility of configuring a minimum number of Pipelines to keep. None of this differentiates by ref.
I might think about Pipelines on my default branch, or protected branches, tags, etc. differently than others, say on merge requests. If I want to get rid of merge request Pipelines after a year but never on my default branch after merge, I can't differentiate so I'll have to keep everything.
A Proposal
-
Add some configurability (not necessarily all existing configuration) by ref. We could still have one age limit (e.g. 1 year) but different minimums for branches and merge requests.
-
Probably wait to see how configuration grows and what customers demand before we get to specific with the proposals here.