blob: bf3aa6c3b02f973473cdd0eaf3a9469ffc3bb149 [file] [log] [blame]
David Ostrovskya7e95e52019-11-02 10:12:49 +01001build --workspace_status_command="python ./tools/workspace_status.py" --strategy=Closure=worker
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 Pursehouse7e6ec142019-05-28 10:42:41 +09005build --java_toolchain //tools:error_prone_warnings_toolchain
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
Thomas Draebing3ccc4cf2019-05-20 15:11:07 +020014test --build_tests_only
15test --test_output=errors
16
David Ostrovskyadb2f752019-10-10 03:47:27 +020017import %workspace%/tools/remote-bazelrc