Practise the standard verbs for speeding up builds with BuildKit cache mounts.
0 / 5 completed
1 / 5
Fill in: 'We ___ a cache mount for the package manager's download directory so a rebuild doesn't re-fetch every dependency from scratch each time.'
We 'add a cache mount' — the standard, established BuildKit collocation for persisting a directory's contents between builds. The other options aren't the recognised term here.
2 / 5
Fill in: 'Skipping a cache mount on a slow dependency install step can ___ every single build re-downloading gigabytes of packages needlessly.'
We say no cache mount will 'leave' every build re-downloading packages — the standard, natural collocation for the resulting waste. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the cache mount's ID per build stage so two unrelated steps don't collide and silently corrupt each other's cached contents.'
We 'scope an ID' — the standard, simple collocation for keeping separate build stages' caches from colliding. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the cache mount deliberately when a lockfile changes, so a stale package version is never silently reused from a previous build.'
We 'invalidate a cache' — the standard, established collocation for deliberately discarding cached contents on a relevant change. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ build time before and after adding a cache mount to confirm it's actually cutting minutes off CI, not just adding complexity.'
We 'compare' build times — the standard, simple collocation for contrasting a metric before and after a change. The other options are less idiomatic here.