remote caching

Storing build outputs on a shared server so that any developer or CI machine with the same inputs can download the result instead of rebuilding.

A writable shared cache that is not access-controlled lets one compromised machine plant malicious build outputs for everyone.

In more detail

When a task’s input hash is found in the remote cache, the tool downloads the saved files and logs and marks the task done in seconds. Because anyone who can write to the cache can influence everyone’s builds, the cache must be protected with access tokens and should separate environments such as staging and production.

Related terms

Taught in

References