ProductBuild & ship

Remote cache

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.

Get startedRead the docs
feat/refund-cap
CodeGraphAtlasTasksJobs
S
1
ToolsPS
1
2
3⌄
4
5
6⌄
7
8
9
10
11
12
13
14⌄
15
16
17
18
load("@rbs//go/rules.rbs", "go_binary", "go_library")
​
go_library(
name = "checkout",
srcs = glob(["*.go"], exclude = ["*_test.go", "main.go"]),
deps = [
"//libs/httpx:httpx",
"//libs/ledgerdb:ledgerdb",
"//libs/money:money",
"//proto/payments:go",
],
)
​
go_binary(
name = "server",
srcs = ["main.go"],
deps = [":checkout"],
)
Terminal 1×
^CClear
/workspace/repo $ git log --oneline -2
a3f9c21 (HEAD -> feat/refund-cap, origin/main) Cap retry backoff
5d20b1e Add idempotency keys to refunds
/workspace/repo $
RBSReadyUTF-8RBS✦ Completions On◇ Show AIHide Activity Bar◀ Hide Explorer⫿ Split🔍 Search● ⎇ Git (0)Hide Terminal

How you use it

Remote cache, step by step.

  1. 01Remote cache

    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.

  2. 02Remote cache

    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.

  3. 03Remote cache

    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.

Coming soon: Bazel remote execution against the cluster; Bazel gets the cache today

The full reference lives in the docs.

Works with

Build systemRemote execution

Open a branch and try it.

Boots in seconds. Your team joins with a link.

Get startedTalk to us