@@ -22,17 +22,26 @@ common --@rules_python//python/config_settings:bootstrap_impl=script
2222# default in bazel 9
2323startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1
2424
25- # buildbuddy
26- # for remote execution of the build. Add `common --config=remote` to
27- # .bazelrc.user
28- common:remote --bes_backend=grpcs://heir.buildbuddy.io
29- common:remote --bes_results_url=https://heir.buildbuddy.io/invocation/
30- common:remote --remote_cache=grpcs://heir.buildbuddy.io
31- common:remote --remote_cache_compression
32- common:remote --remote_timeout=10m
25+ # BuildBuddy
26+ build --bes_results_url=https://heir.buildbuddy.io/invocation/
27+ build --bes_backend=grpcs://heir.buildbuddy.io
28+ common --noremote_upload_local_results # Uploads logs & artifacts without writing to cache
29+ common --remote_cache=grpcs://heir.buildbuddy.io
30+ common --remote_cache_compression
31+ common --remote_header=x-buildbuddy-api-key=IqGGzfrvMgDJh927qtrw
32+ common --remote_timeout=10m
33+
34+ # This enables remote build execution and writing to the remote cache, which
35+ # dramatically speeds up builds. Add a .bazelrc.user file with:
36+ #
37+ # common --remote_header=x-buildbuddy-api-key=<YOUR_API_KEY>
38+ # common --config=remote
39+ #
40+ # Note this requires a buildbuddy.io account and API key. The default
41+ # API key used above is read-only.
3342common:remote --extra_execution_platforms=@llvm//:rbe_platform
3443common:remote --jobs=500
35- common:remote --remote_executor=grpcs://heir .buildbuddy.io
44+ common:remote --remote_executor=grpcs://remote .buildbuddy.io
3645
3746# CI executions are always remote, and have extra build metadata
3847common:ci --build_metadata=ROLE=CI
0 commit comments