blob: 6ccd56a74fab94242dcd6caf8127111f3e59fb88 [file] [log] [blame]
David Ostrovsky2b5fe092021-03-03 11:52:30 +01001build --workspace_status_command="python3 ./tools/workspace_status.py"
David Ostrovsky2bf355d2018-05-30 08:58:22 +02002build --repository_cache=~/.gerritcodereview/bazel-cache/repository
Wyatt Allen370962b2018-06-08 15:45:02 -07003build --action_env=PATH
Han-Wen Nienhuys9c15e2b2019-05-16 16:59:33 +02004build --disk_cache=~/.gerritcodereview/bazel-cache/cas
David Ostrovskyb89332d2020-04-27 07:06:24 +02005build --java_toolchain=//tools:error_prone_warnings_toolchain_java11
Han-Wen Nienhuys9c15e2b2019-05-16 16:59:33 +02006
Gert van Dijka5c54892019-09-19 11:57:16 +02007# Enable strict_action_env flag to. For more information on this feature see
8# https://groups.google.com/forum/#!topic/bazel-discuss/_VmRfMyyHBk.
9# This will be the new default behavior at some point (and the flag was flipped
10# shortly in 0.21.0 - https://github.com/bazelbuild/bazel/issues/7026). Remove
11# this flag here once flipped in Bazel again.
12build --incompatible_strict_action_env
13
David Ostrovsky2a3b2822021-02-19 12:58:35 +010014build --announce_rc
15
David Ostrovskybd296eb2021-04-14 15:54:59 +020016# Workaround Bazel worker crash (remove after upgrading to 4.1.0)
17# https://github.com/bazelbuild/bazel/issues/13333
18build --experimental_worker_multiplex=false
19
Thomas Draebing3ccc4cf2019-05-20 15:11:07 +020020test --build_tests_only
21test --test_output=errors
Luca Milanesio980a8f02020-10-06 13:44:22 +010022test --java_toolchain=//tools:error_prone_warnings_toolchain_java11
Thomas Draebing3ccc4cf2019-05-20 15:11:07 +020023
David Ostrovskyadb2f752019-10-10 03:47:27 +020024import %workspace%/tools/remote-bazelrc