Cache

The content-addressed store magus consults before running a target, so unchanged work is skipped.

Elsewhere

Bazel's action cache and Gradle's build cache are the same idea: work keyed by a hash of its inputs. An HTTP cache keys a response by URL and headers instead. A magus cache entry is keyed by the inputs a target declares, so an undeclared input is a bug the sandbox reports.

Example

A second run of an unchanged target replays from the cache instead of running.

magus run build libs/xdg

Used in

In the docs:

• S5: Warm cache replay
• Cache model
• GitHub Actions cache
• Readiness never keys the cache
• The shared cache
• Shared cache trust

In the code (magus refs <name> lists every site):

• cache.Cache (Go)
• config.Cache (Go)

See also

• Cache model
• Remote cache
• Sandbox