summaryrefslogtreecommitdiffhomepage
path: root/.bazelrc
diff options
context:
space:
mode:
authorNicolas Lacasse <nlacasse@google.com>2019-08-13 11:20:43 -0700
committergVisor bot <gvisor-bot@google.com>2019-08-13 11:21:55 -0700
commitfa3d0e6f63d6ecc9a6566ec80e4a8c7519c6cf76 (patch)
tree20d52584852bec4e2fc8b52c79260195cded0c0f /.bazelrc
parent9769a8eaa4b384d1b7db9f06edf28a6331cd2b64 (diff)
Bump Bazel to v0.28.0
The new version has a change in behavior when using a custom platform: * Old behavior: rules that don't require a toolchain used host_platform, no matter what execution platforms are specified. * New behavior: rules that don't require a toolchain use standard platform resolution that starts with execution platforms. As part of this change, we cannot use the "extra_exectution_platforms" flag provided by the default bazelrc. I got rid of the default bazelrc file, and made our custom .bazelrc as minimal as possible. PiperOrigin-RevId: 263176802
Diffstat (limited to '.bazelrc')
-rw-r--r--.bazelrc28
1 files changed, 18 insertions, 10 deletions
diff --git a/.bazelrc b/.bazelrc
index f6b21086d..eda884473 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -12,26 +12,34 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-# Start with a base bazelrc for a recent version of bazel. These can be
-# downloaded from:
-# https://github.com/bazelbuild/bazel-toolchains/tree/master/bazelrc
-import %workspace%/tools/bazel-0.24.0.bazelrc
-
-# All changes below are gVisor-specific.
-
# Display the current git revision in the info block.
build --workspace_status_command tools/workspace_status.sh
-# Add a custom toolchain that builds in a privileged docker container, which is
-# required by our syscall tests.
+# Enable remote execution so actions are performed on the remote systems.
+build:remote --remote_executor=grpcs://remotebuildexecution.googleapis.com
+
+# Add a custom platform and toolchain that builds in a privileged docker
+# container, which is required by our syscall tests.
+build:remote --host_platform=//test:rbe_ubuntu1604
build:remote --extra_toolchains=//test:cc-toolchain-clang-x86_64-default
build:remote --extra_execution_platforms=//test:rbe_ubuntu1604
-build:remote --host_platform=//test:rbe_ubuntu1604
build:remote --platforms=//test:rbe_ubuntu1604
+# Use default image for crosstool toolchain.
+build:remote --crosstool_top=@rbe_default//cc:toolchain
+
+# Default parallelism and timeout for remote jobs.
+build:remote --jobs=50
+build:remote --remote_timeout=3600
+
# RBE requires a strong hash function, such as SHA256.
startup --host_jvm_args=-Dbazel.DigestFunction=SHA256
+# Enable authentication. This will pick up application default credentials by
+# default. You can use --google_credentials=some_file.json to use a service
+# account credential instead.
+build:remote --google_default_credentials=true
+
# Auth scope needed for authentication with RBE.
build:remote --auth_scope="https://www.googleapis.com/auth/cloud-source-tools"