Build Cache
Avrea's build cache stores compilation artifacts in colocated cache so that rebuilds only recompile what actually changed. This works across jobs, branches, and workflow runs.
Supported tools
Section titled “Supported tools”| Tool | Mechanism | Auto-configured |
|---|---|---|
| Bazel | HTTP remote cache | Yes |
| ccache | HTTP remote storage | Yes |
| Go | GOCACHEPROG (Go 1.24+) | Yes |
| Gradle | HttpBuildCache | Yes |
| Maven | Build cache extension | Yes |
| Nix | Binary cache substituter | Yes |
| Nx | Self-hosted remote cache | Yes |
| sccache | WebDAV remote storage | Yes |
| Turborepo | Remote cache API | Yes |
| Xcode | Compilation cache (macOS) | Yes |
How it works
Section titled “How it works”On Avrea runners, build cache environment variables and configuration files are pre-configured before your workflow steps run. Each tool connects to the colocated build cache.
The cache.avrea.com hostname used in examples throughout this section resolves
only inside Avrea runners — it points to the colocated cache via the runner's
host file. The URLs are not reachable from a developer laptop.