21 / 48 · 16 CI/CD Pipelines · Artifact Management← prev⊞ allnext →☰ Read as one page
4.3Retention Policies
Artifacts consume storage. Set retention policies that balance debugging needs with costs.
| Artifact Type | Passing Runs | Failing Runs | Rationale |
|---|---|---|---|
| Test reports (XML/HTML) | 7 days | 30 days | Failing reports are needed for investigation |
| Screenshots/traces | Do not upload | 14 days | Only useful for debugging failures |
| Coverage reports | 30 days | 30 days | Needed for trend analysis |
| Logs | 3 days | 14 days | Useful for root cause analysis |
| HAR files | Do not upload | 7 days | Large files; only needed for API debugging |
# GitHub Actions retention configuration
- uses: actions/upload-artifact@v4
with:
name: test-report
path: test-results/
retention-days: 14 # Override default (90 days)