Caching
Warm cache
Quick answer
A warm cache already contains the entries a job needs, so work is restored rather than recomputed.
A warm cache already contains the entries a job needs, so work is restored rather than recomputed.
Why it matters
The first run after a dependency change is always cold. What matters is how quickly the cache re-warms and whether every branch benefits or only the one that paid for it.
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
Artifact cacheAn artifact cache stores build outputs between CI runs so that unchanged work does not have to be recomputed.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.