adb2f7505b
Support for Remote Bazel Execution was added in this change: Ia18e5fd55f8. However, the import statement in .bazelrc: import tools/remote-bazelrc missed to prefix the tools directory with %workspace% prefix and thus broke running the build from non root-workspace directory. Change-Id: I85673659138e23d25eaecf40606d57706fe9f6e1
18 lines
779 B
Plaintext
18 lines
779 B
Plaintext
build --workspace_status_command=./tools/workspace-status.sh --strategy=Closure=worker
|
|
build --repository_cache=~/.gerritcodereview/bazel-cache/repository
|
|
build --action_env=PATH
|
|
build --disk_cache=~/.gerritcodereview/bazel-cache/cas
|
|
build --java_toolchain //tools:error_prone_warnings_toolchain
|
|
|
|
# Enable strict_action_env flag to. For more information on this feature see
|
|
# https://groups.google.com/forum/#!topic/bazel-discuss/_VmRfMyyHBk.
|
|
# This will be the new default behavior at some point (and the flag was flipped
|
|
# shortly in 0.21.0 - https://github.com/bazelbuild/bazel/issues/7026). Remove
|
|
# this flag here once flipped in Bazel again.
|
|
build --incompatible_strict_action_env
|
|
|
|
test --build_tests_only
|
|
test --test_output=errors
|
|
|
|
import %workspace%/tools/remote-bazelrc
|