Caching
Artifact cache
Quick answer
An artifact cache stores build outputs between CI runs so that unchanged work does not have to be recomputed.
An artifact cache stores build outputs between CI runs so that unchanged work does not have to be recomputed.
Why it matters
The distinction from an artifact store matters: a cache is an optimisation that may be evicted at any time, so a build must still succeed on a cold cache. If your pipeline breaks when the cache misses, you have a dependency, not a cache.
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
Cache evictionCache eviction is the removal of cache entries to stay within a size limit, usually by discarding the least recently used entries first.Cache hit rateCache hit rate is the proportion of cache lookups that find a usable entry, expressed as a percentage.Cache keyA cache key is the string that identifies a cache entry, typically built from a hash of the lockfiles that determine the cached content.Cache scopeCache scope defines which workflows, branches and repositories may read a given cache entry.