productbuild & ship
rbs build //services/checkout:image
Build once for the whole team. And every agent.
Every branch server is attached to your organization’s cache the moment it boots. If a teammate or an agent built it, you do not. Nothing to configure.
how you use it
Remote cache, in order.
01
You never set it up
When a branch opens, the control plane hands its server a short-lived cache credential for your organization: twelve hours, minted per machine, never shown in a browser. The first build on the branch already reads what other branches, agents and CI wrote.
02
The agent’s loop: fifty branches, one store
Fifty agent branches on the same commit build the same targets once. Only passing test results are stored, a cached test re-checks its coverage floor, and a filtered run is never cached. CI runs read the same store.
03
Bazel speaks to it too
The cache implements the Remote Execution API, so a Bazel workspace in the same organization points at it with one flag and shares the store. Usage per organization shows in the hub.
Remote Execution API: Capabilities, CAS, ActionCache, ByteStream, compressed blobs; content-defined chunking for transfer.
not built yet: Bazel remote execution against the cluster; Bazel gets the cache today
The full reference lives in the docs.
works with
Open a branch and try it.
Boots in seconds. Your team joins with a link.