| 1 |
# Copyright 2022 The Bazel Authors. All rights reserved. |
| 2 |
# |
| 3 |
# Licensed under the Apache License, Version 2.0 (the "License"); |
| 4 |
# you may not use this file except in compliance with the License. |
| 5 |
# You may obtain a copy of the License at |
| 6 |
# |
| 7 |
# http://www.apache.org/licenses/LICENSE-2.0 |
| 8 |
# |
| 9 |
# Unless required by applicable law or agreed to in writing, software |
| 10 |
# distributed under the License is distributed on an "AS IS" BASIS, |
| 11 |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 12 |
# See the License for the specific language governing permissions and |
| 13 |
# limitations under the License. |
| 14 |
|
| 15 |
# This file is auto-generated from release/bazelrc.tpl and should not be |
| 16 |
# modified directly. |
| 17 |
|
| 18 |
# This .bazelrc file contains all of the flags required for the provided |
| 19 |
# toolchain with Remote Build Execution. |
| 20 |
# |
| 21 |
# This .bazelrc file also contains all of the flags required for the local |
| 22 |
# docker sandboxing. |
| 23 |
|
| 24 |
# Depending on how many machines are in the remote execution instance, setting |
| 25 |
# this higher can make builds faster by allowing more jobs to run in parallel. |
| 26 |
# Setting it too high can result in jobs that timeout, however, while waiting |
| 27 |
# for a remote machine to execute them. |
| 28 |
build:remote --jobs=200 |
| 29 |
build:remote --disk_cache= |
| 30 |
|
| 31 |
# Set several flags related to specifying the platform, toolchain and java |
| 32 |
# properties. |
| 33 |
build:remote --crosstool_top=@rbe_jdk11//cc:toolchain |
| 34 |
build:remote --extra_toolchains=@rbe_jdk11//config:cc-toolchain |
| 35 |
build:remote --extra_execution_platforms=@rbe_jdk11//config:platform |
| 36 |
build:remote --host_platform=@rbe_jdk11//config:platform |
| 37 |
build:remote --platforms=@rbe_jdk11//config:platform |
| 38 |
build:remote --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 |
| 39 |
|
| 40 |
# Set various strategies so that all actions execute remotely. Mixing remote |
| 41 |
# and local execution will lead to errors unless the toolchain and remote |
| 42 |
# machine exactly match the host machine. |
| 43 |
build:remote --define=EXECUTOR=remote |
| 44 |
|
| 45 |
# Enable the remote cache so action results can be shared across machines, |
| 46 |
# developers, and workspaces. |
| 47 |
build:remote --remote_cache=remotebuildexecution.googleapis.com |
| 48 |
|
| 49 |
# Enable remote execution so actions are performed on the remote systems. |
| 50 |
build:remote --remote_executor=remotebuildexecution.googleapis.com |
| 51 |
|
| 52 |
# Set a higher timeout value, just in case. |
| 53 |
build:remote --remote_timeout=3600 |
| 54 |
|
| 55 |
# Enable authentication. This will pick up application default credentials by |
| 56 |
# default. You can use --auth_credentials=some_file.json to use a service |
| 57 |
# account credential instead. |
| 58 |
build:remote --google_default_credentials |
| 59 |
|
| 60 |
# The following flags enable the remote cache so action results can be shared |
| 61 |
# across machines, developers, and workspaces. |
| 62 |
build:remote-cache --remote_cache=remotebuildexecution.googleapis.com |
| 63 |
build:remote-cache --tls_enabled=true |
| 64 |
build:remote-cache --remote_timeout=3600 |
| 65 |
build:remote-cache --auth_enabled=true |