Practise the standard verbs for building an effective GitLab CI cache strategy.
0 / 5 completed
1 / 5
Fill in: 'We ___ the cache key to the lockfile's hash so a dependency change automatically busts the cache instead of silently reusing outdated packages.'
We 'tie a key' — the standard, simple collocation for linking a cache's identity to a value that changes when the cache should. The other options are less idiomatic here.
2 / 5
Fill in: 'Using a single fixed cache key across every branch can ___ two pipelines running concurrently overwriting each other's cached dependencies mid-job.'
We say a shared cache key will 'leave' concurrent jobs overwriting each other — the standard, natural collocation for the resulting corruption. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the cache per job stage rather than globally, so an unrelated job further down the pipeline doesn't restore a cache meant for a completely different step.'
We 'scope a cache' — the standard, simple collocation for restricting a cache's use to the stages that actually need it. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ pipeline duration before and after introducing a cache to confirm it's actually saving minutes, not just adding an extra restore step to every job.'
We 'compare' durations — the standard, simple collocation for contrasting a metric before and after a change. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a stale cache deliberately when a build starts behaving oddly, since a corrupted cache entry can silently reproduce the same failure on every subsequent run.'
We 'clear a cache' — the standard, established collocation for deliberately discarding stored contents suspected of being corrupted. The other options aren't the recognised term here.