Skip to content

ci: keep CI artifacts days, not months - #749

Open
aldoruizluna wants to merge 1 commit into
mainfrom
ci/artifact-retention-2026-10-26
Open

aldoruizluna wants to merge 1 commit into
mainfrom
ci/artifact-retention-2026-10-26

Conversation

@aldoruizluna

Copy link
Copy Markdown
Collaborator

Why

Uploads across madfam-org are failing with «Failed to CreateArtifact: Artifact storage quota has been hit». crea-map e2e shards on 2026-10-24/25 are one example. A survey of live artifacts on 2026-10-26 found the bytes held mostly in a few public repos with long retention:

Repo Artifact Live size Retention
janua api-coverage-report 660 MiB 30 d
janua frontend-build 241 MiB 90 d (default)
madfam-site playwright-report 205 MiB 14 d
tezca frontend-coverage-node* 201 MiB 90 d (default)
janua playwright-report 86 MiB 30 d

What changes

  • tests.yml: api-coverage-report 30 → 3 days. coverage-gate downloads it in the same run, and Codecov keeps the history. The journeys playwright-report goes 30 → 7.
  • pr-quality.yml: frontend-build (.next + dist) gets 1 day. No workflow downloads it; it was on the 90-day default.
  • e2e-tests.yml and validate-user-journeys.yml: 30 → 7 days.

What merging deploys

Nothing. These are CI workflow files only; no deploy workflow, image or runtime changes. In production nothing changes. Only artifacts uploaded after the merge get the shorter retention; existing artifacts keep their expiry. No artifact is deleted.

🤖 Generated with Claude Code

api-coverage-report 30 -> 3 days (read in the same run by coverage-gate), frontend-build 90 -> 1 day (no consumer), Playwright reports and journey results 30 -> 7 days.

The org-wide artifact storage quota is full (uploads fail with «Artifact
storage quota has been hit»), and this repo is among the largest holders
of stored artifact bytes. Only new uploads are affected; existing
artifacts keep their original expiry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

📚 Documentation checks found issues. Please review the maintenance script output.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Code quality checks found issues. Please review the maintenance script output.

@github-actions

Copy link
Copy Markdown
Contributor

Security Scan Summary

Date: Mon Oct 26 09:11:25 UTC 2026
Commit: 11dafc9

Scan Results

  • CodeQL: success
  • Python Security: success
  • JavaScript Security: success
  • Secrets Scan: success
  • Container Scan: success
  • DAST ZAP: skipped

@github-actions

Copy link
Copy Markdown
Contributor

🎭 Playwright E2E Test Results

  • Total: 11
  • Passed: 11 ✅
  • Failed: 0 ❌
  • Flaky: 0 ⚠️
  • Skipped: 0 ⏭️

Full Report

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants