One build tool everywhere
Every project builds with Bazel, at a version pinned in the repository, so the same commands work in every repo.
One build tool everywhere
Every project builds with Bazel, at a version pinned in the repository, so the same commands work in every repo.
Tools pinned in the repo
Programs a build runs (Chromium, ffmpeg, Python, Node) are pinned by the repository, not installed on the machine or baked into a Docker image.
Shared, trusted cache
A build step whose inputs haven’t changed is never run twice. Results come from a shared remote cache that only trusted machines can write to.
This handbook is adapted from SVRBC’s. Most of the infrastructure it describes (the fork group, the review bot, the build cache, the AWS account) is not yet set up for Inky Labs; pages say so where it matters.