~/.bazelrc to point at this endpoint and benefit from the same remote cache hits and remote execution workers that CI uses, without accessing the internal VPC.
The external remote cache is a separate cache cluster that complies with the Bazel Remote Execution Protocol v2. The external remote execution cluster accepts build actions from developer machines and runs them on dedicated workers for the target platform architecture (x86-64, arm64, or custom).
The external cache can be configured in either of two modes:
- Independent storage (the default) — the external cache has its own backing storage, sized and scaled separately from the internal CI cache. Use this when you want to isolate CI’s cache from developer traffic.
- Pass-through — the external cache reuses the internal CI cache as its upstream storage, so a cache entry written by a CI runner becomes available to developer workstations immediately, and vice versa. This is the lowest-friction setup when you want CI and developer caches to share hits without operating two storage layers.
--remote_header=X-Aspect=aw_pat_XXXX — convenient for local development on a workstation where an interactive OIDC flow isn’t a fit.