ee03408c44
Migrates to using larger resource classes for windows CI runs as well as updating the bazel rcs for windows and linux to use all/more of the resources available in the executors PR Close #39124
31 lines
1.5 KiB
Plaintext
31 lines
1.5 KiB
Plaintext
# These options are enabled when running on CI
|
|
# We do this by copying this file to /etc/bazel.bazelrc at the start of the build.
|
|
# See documentation in /docs/BAZEL.md
|
|
|
|
# Import config items common to both Linux and Windows setups.
|
|
# https://docs.bazel.build/versions/master/guide.html#bazelrc-syntax-and-semantics
|
|
try-import %workspace%/.circleci/bazel.common.rc
|
|
|
|
# Save downloaded repositories in a location that can be cached by CircleCI. This helps us
|
|
# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
|
|
build --repository_cache=/home/circleci/bazel_repository_cache
|
|
|
|
# Workaround https://github.com/bazelbuild/bazel/issues/3645
|
|
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
|
|
# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
|
|
# https://circleci.com/docs/2.0/configuration-reference/#resource_class
|
|
build --local_cpu_resources=20
|
|
build --local_ram_resources=32768
|
|
|
|
# All build executed remotely should be done using our RBE configuration.
|
|
build:remote --google_default_credentials
|
|
|
|
# Upload to GCP's Build Status viewer to allow for us to have better viewing of execution/build
|
|
# logs. This is only done on CI as the BES (GCP's Build Status viewer) API requires credentials
|
|
# from service accounts, rather than end user accounts.
|
|
build:remote --bes_backend=buildeventservice.googleapis.com
|
|
build:remote --bes_timeout=30s
|
|
build:remote --bes_results_url="https://source.cloud.google.com/results/invocations/"
|
|
|
|
build --config=remote
|