Transport temporary data between jobs using caching
Pipelines should assume that the cache must be rebuilt
The cache keyword defines what and when to push and pull
One job downloads or generates data and pushes to the cache
Subsequent jobs can pull from the cache to hit the ground running
Examples for many programming languages
| Type | Availability |
|---|---|
| Local | available on the same runner with Docker executor |
| Distributed | requires an S3-compatible backend (e.g. AWS S3 , MinIO , Ceph ) |
Runner local cache