Practise vocabulary for build caching: cache hits and misses, cache keys, remote caching, determinism, and CI cache strategies.
0 / 5 completed
1 / 5
A build ___ occurs when the tool finds a previous result matching the current inputs and reuses it instead of rebuilding.
A cache hit means the build tool found a matching cached output for the current input fingerprint. The task is skipped and the cached output is replayed, saving build time.
2 / 5
The ___ uniquely identifies a cached build artifact based on all inputs: source files, dependencies, environment variables, and build flags.
The cache key is a fingerprint computed from all inputs to a build task. Any change to inputs produces a different key, triggering a cache miss and a fresh rebuild.
3 / 5
A build is ___ if the same source inputs always produce byte-for-byte identical outputs, enabling reliable remote caching.
Deterministic builds produce identical outputs given identical inputs, regardless of when or where the build runs. Non-determinism (timestamps embedded in outputs) defeats caching.
4 / 5
'Warming the cache' in CI refers to ___.
Cache warming runs a preliminary build or restore step to populate the cache, so the main build run benefits from cache hits immediately rather than rebuilding everything from scratch.
5 / 5
A ___ cache stores build outputs remotely so multiple developers and CI machines can share results.
A remote cache (S3, GCS, or a dedicated cache server) allows any machine with network access to retrieve previously computed build outputs. This makes cache hits available across the entire team, not just a single machine.