gilescope/rebuck

Persistent buck2 action cache on GitHub Actions via a bazel-remote sidecar (RE + buck).

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
bazel-remote-versionbazel-remote release version to install.2.6.1
max-size-gbbazel-remote on-disk LRU cap, in GiB. Bound this so the cache fits the 10GB GHA budget.2
grpc-portLocalhost gRPC port bazel-remote serves the REAPI on.9092
http-portLocalhost HTTP port for the /status health + stats endpoint.8080
cache-dirDirectory bazel-remote stores blobs in (and the actions/cache path). Defaults to ~/.cache/rebuck.""
cache-key-prefixPrefix for the actions/cache key.rebuck
execution-platformbuck2 target providing the remote-cache execution platform (see examples/platforms).root//platforms:re-cache
write-buckconfig-localWrite .buckconfig.local with the RE client + execution_platforms config so your `buck build` needs no extra flags. Set false to manage buck config yourself.true
buck-rootDirectory of your buck2 project root (where .buckconfig lives), relative to the workspace or absolute. .buckconfig.local is written here. Defaults to the workspace root.""
force-cache-uploadExport BUCK2_TEST_FORCE_CACHE_UPLOAD=1. The prelude marks rustc compile actions allow_cache_upload=False; without this their outputs (the bulk of the build) are never uploaded.true
namedescription
grpc-addressThe grpc:// address buck2 should use for the RE cache (set via core.setOutput).