| # |
| # Licensed to the Apache Software Foundation (ASF) under one or more |
| # contributor license agreements. See the NOTICE file distributed with |
| # this work for additional information regarding copyright ownership. |
| # The ASF licenses this file to You 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. |
| # |
| startup --host_jvm_args=-Xmx2g |
| |
| run --color=yes |
| |
| build --color=yes |
| build --enable_platform_specific_config |
| |
| test --action_env=TEST_TMPDIR=/tmp |
| |
| test --experimental_strict_java_deps=warn |
| build --experimental_strict_java_deps=warn |
| |
| |
| # This .bazelrc file contains all of the flags required for the provided |
| # toolchain with Remote Build Execution. |
| # Note your WORKSPACE must contain an rbe_autoconfig target with |
| # name="rbe_default" to use these flags as-is. |
| |
| # 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=150 |
| |
| # Set several flags related to specifying the platform, toolchain and java |
| # properties. |
| # These flags should only be used as is for the rbe-ubuntu16-04 container |
| # and need to be adapted to work with other toolchain containers. |
| build:remote --java_runtime_version=rbe_jdk |
| build:remote --tool_java_runtime_version=rbe_jdk |
| build:remote --extra_toolchains=@rbe_default//java:all |
| |
| build:remote --crosstool_top=@rbe_default//cc:toolchain |
| build:remote --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 |
| # Platform flags: |
| # The toolchain container used for execution is defined in the target indicated |
| # by "extra_execution_platforms", "host_platform" and "platforms". |
| # More about platforms: https://docs.bazel.build/versions/master/platforms.html |
| build:remote --extra_toolchains=@rbe_default//config:cc-toolchain |
| build:remote --extra_execution_platforms=@rbe_default//config:platform |
| build:remote --host_platform=@rbe_default//config:platform |
| build:remote --platforms=@rbe_default//config:platform |
| |
| # Starting with Bazel 0.27.0 strategies do not need to be explicitly |
| # defined. See https://github.com/bazelbuild/bazel/issues/7480 |
| build:remote --define=EXECUTOR=remote |
| |
| # Enable remote execution so actions are performed on the remote systems. |
| build:remote --remote_executor=grpcs://remote.buildbuddy.io |
| |
| # Enforce stricter environment rules, which eliminates some non-hermetic |
| # behavior and therefore improves both the remote cache hit rate and the |
| # correctness and repeatability of the build. |
| build:remote --incompatible_strict_action_env=true |
| |
| # Set a higher timeout value, just in case. |
| build:remote --remote_timeout=3600 |
