Guides
How to publish build artifacts
Artifact storage costs are growing and retention was never configured.
4 min read
Artifact storage costs are growing and retention was never configured.
Why it happens
The 90-day default retention applies to everything uploaded, including large intermediates.
How to fix it
- Set short retention for intermediates and long retention only for releases
- Upload only what someone will actually download
- Use a cache keyed on the run ID for job-to-job handoff instead of an artifact
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.