Guides
How to pass data between jobs
Jobs need to share build output and it is unclear how.
4 min read
Jobs need to share build output and it is unclear how.
Why it happens
Jobs run on separate machines with separate filesystems.
How to fix it
- Use job outputs for small values like a version string or digest
- Use artifacts for files, with short retention for intermediates
- Use a cache keyed on the run ID for large intermediates — usually cheaper than artifacts
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.