Epic Goal

Enable defining multiple retention policies for the pipeline data stored in Tekton Results.  ** At this moment, retention based on no.of days is already available.

Why is this important?

Customers require different retention period for different pipelines, how long do they want to retain in the DB. For example, if a pipeline is used for deploying to production requires very long retention while a pipeline that builds java artifacts requires short retention.

Scenarios

• Based on events type eg: comment, PR, push
• Deployments to production need longer retention compared to test pipelines
• Based on chains labels eg: failed annotation ones need higher/lower retention

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Admin can define multiple retention policies for Tekton Results
• Each retention policy would apply to one or multiple pipelines 
• A retention policy would describe which pipelines and for how long should be retained

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. what needs to be supported?
2.  

Work pending:

1. Modify TEP based on the open questions

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment