Set artifact retention so storage stops growing
Build artefacts kept forever by default, given a retention policy with the storage trend attached.
The ticket
Define and apply a retention policy for build artefacts.
Acceptance criteria
- A retention period is set per artefact type with a rationale
- Artefacts needed for compliance or rollback are excluded and named
- The storage trend is attached before and after
- The policy is documented where the pipeline is documented
What lands as proof
The storage trend before and after, with the excluded artefact types named explicitly.
Why teams defer it
- Storage is cheap per build and expensive per year, and nobody sees the annual number.
- Deleting an artefact somebody needed for a rollback is unrecoverable, so the exclusions matter more than the policy.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: define and apply a retention policy for build artefacts. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means policy documented, storage trend attached, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.