Create a data retention limit for a group or namespace for CI pipelines

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The Problem

I suspect that customers with lots of namespaces and Projects will find it tedious or unworkable to configure a separate pipeline retention policy for each individual project.

There may be a correlation between the size of a customer namespace and the desire to use this feature to save space.

A Proposal

I propose we add a cascading Namespace setting, so a universal policy can be defined that will affect all Projects, and then be optionally overridden at the Project level.