| # Copyright 2016 The Bazel Authors. All rights reserved. |
| # |
| # Licensed under the Apache License, Version 2.0 (the "License"); |
| # you may not use this file except in compliance with the License. |
| # You may obtain a copy of the License at |
| # |
| # http://www.apache.org/licenses/LICENSE-2.0 |
| # |
| # Unless required by applicable law or agreed to in writing, software |
| # distributed under the License is distributed on an "AS IS" BASIS, |
| # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| # See the License for the specific language governing permissions and |
| # limitations under the License. |
| |
| # This file is auto-generated from release/bazelrc.tpl and should not be |
| # modified directly. |
| |
| # This .bazelrc file contains all of the flags required for the provided |
| # toolchain with Remote Build Execution. |
| # |
| # This .bazelrc file also contains all of the flags required for the local |
| # docker sandboxing. |
| |
| # Depending on how many machines are in the remote execution instance, setting |
| # this higher can make builds faster by allowing more jobs to run in parallel. |
| # Setting it too high can result in jobs that timeout, however, while waiting |
| # for a remote machine to execute them. |
| build:remote --jobs=50 |
| build:remote --disk_cache= |
| |
| # Set several flags related to specifying the platform, toolchain and java |
| # properties. |
| build:remote --host_javabase=@rbe_jdk11//java:jdk |
| build:remote --javabase=@rbe_jdk11//java:jdk |
| build:remote --crosstool_top=@rbe_jdk11//cc:toolchain |
| build:remote --extra_toolchains=@rbe_jdk11//config:cc-toolchain |
| build:remote --extra_execution_platforms=@rbe_jdk11//config:platform |
| build:remote --host_platform=@rbe_jdk11//config:platform |
| build:remote --platforms=@rbe_jdk11//config:platform |
| build:remote --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 |
| |
| # Set various strategies so that all actions execute remotely. Mixing remote |
| # and local execution will lead to errors unless the toolchain and remote |
| # machine exactly match the host machine. |
| build:remote --spawn_strategy=remote,sandboxed |
| build:remote --strategy=Javac=remote |
| build:remote --strategy=Genrule=remote |
| build:remote --define=EXECUTOR=remote |
| |
| # Enable the remote cache so action results can be shared across machines, |
| # developers, and workspaces. |
| build:remote --remote_cache=remotebuildexecution.googleapis.com |
| |
| # Enable remote execution so actions are performed on the remote systems. |
| build:remote --remote_executor=remotebuildexecution.googleapis.com |
| |
| # Set a higher timeout value, just in case. |
| build:remote --remote_timeout=3600 |
| |
| # Enable authentication. This will pick up application default credentials by |
| # default. You can use --auth_credentials=some_file.json to use a service |
| # account credential instead. |
| build:remote --auth_enabled=true |
| |
| # The following flags enable the remote cache so action results can be shared |
| # across machines, developers, and workspaces. |
| build:remote-cache --remote_cache=remotebuildexecution.googleapis.com |
| build:remote-cache --tls_enabled=true |
| build:remote-cache --remote_timeout=3600 |
| build:remote-cache --auth_enabled=true |
| build:remote-cache --spawn_strategy=standalone |
| build:remote-cache --strategy=Javac=standalone |
| build:remote-cache --strategy=Genrule=standalone |
