-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use BAZEL_BUILD_EXTRA_OPTIONS
to setup Bazel remote cache
#32989
Comments
@Winbobob sgtm we have been gradually shifting configs into are you up for raising a PR to adjust the dev docs? the readme you linked is pretty hopelessly out of date - its on my agenda to do some work on dev docs - but for now i think its the best place (for ref there is also bazel/README amongst others) |
Cool, thank you for the confirmation! I can create the PR. |
@moderation the easiest way to use RBE ive found is to place just the credentials in
and then after doing this is the closest to what ci is doing using bazel directly you want something like:
depending on the toolchain you want you probably also need something like:
|
Title
Use
BAZEL_BUILD_EXTRA_OPTIONS
to setup Bazel remote cacheDescription
The example command mentioned in this README does not work well when you need to specify the header for remote cache.
This is because both
basic
andbearer
AuthN schemes need the quotes to group the content and use quotes here can be tricky. Especially there are already two layers of quotes with in./ci/run_envoy_docker.sh
.Proposal
Update this README:
BAZEL_BUILD_EXTRA_OPTIONS
env variables.user.bazelrc
files.The text was updated successfully, but these errors were encountered: