Use `BAZEL_BUILD_EXTRA_OPTIONS` to setup Bazel remote cache about envoy HOT 5 CLOSED

@Winbobob sgtm

we have been gradually shifting configs into .bazelrc and away from env vars or cli flags for the reasons you point out and many others also

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)

from envoy.

@phlax

from envoy.

Cool, thank you for the confirmation! I can create the PR.

from envoy.

After a couple of years of enjoying the Google RBE, my builds now download GBs of *.dwo files and the builds are now super slow and serial.

I'm guessing my ~/.bazelrc is out of date but haven't been able to work out the right commands

from envoy.

@moderation the easiest way to use RBE ive found is to place just the credentials in user.bazelrc - ie:

build --google_credentials=./gcloud.token

and then after doing export ENVOY_RBE=1 use the ci/do_ci.sh targets

this is the closest to what ci is doing

using bazel directly you want something like:

build --remote_instance_name=projects/envoy-ci/instances/default_instance
build --remote_cache=grpcs://remotebuildexecution.googleapis.com
build --remote_executor=grpcs://remotebuildexecution.googleapis.com
build --jobs=40

depending on the toolchain you want you probably also need something like:

build --config=rbe-toolchain-clang-libc++

from envoy.