Artifacts Usage Report - May 2026 #34391
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-05-25T06:54:09.101Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary Statistics:
📊 Storage by Artifact Type
View All Artifact Types (45 total)
🔍 Key Insights
Largest Storage Consumers
GitHub Pages Build: 7.13 GB (56.0% of total)
Agent Execution Logs: 2.01 GB (15.7% of total)
gh-aw-linux-amd64: 1.56 GB (12.3% of total)
Artifact Distribution Patterns
Storage Trends
💡 Recommendations
Immediate Actions
Optimize GitHub Pages Artifacts (Saves ~7 GB)
Review Binary Retention (Saves ~1.5 GB)
Compress Large Artifacts (Saves ~2 GB)
Long-term Optimizations
Implement Tiered Retention
Artifact Deduplication
Monitoring and Alerts
Expected Impact
Implementing all recommendations could reduce storage by:
📈 Artifact Lifecycle
Based on the analysis of 4,757 artifacts from 810 workflow runs:
🔬 Sample Workflow Analysis
Based on 18 recently active workflows:
gh-awRWZCXM.dockerbuild (1)gh-awX7JIS3.dockerbuild (1)gh-awK1CGUA.dockerbuild (1), agent (1), activation (1)📋 Methodology
Data Collection:
Limitations:
Tools Used:
gh) for API accessReport Generated: 2026-05-24 06:51 UTC
Workflow Run: §26354336826
Beta Was this translation helpful? Give feedback.
All reactions