diff options
| author | Tom Renn <tomrenn@google.com> | 2021-04-26 19:10:52 -0700 |
|---|---|---|
| committer | Tom Renn <tomrenn@google.com> | 2021-05-03 22:50:45 +0000 |
| commit | 9d2347cf85dd54921725df33a1a77745a770d03e (patch) | |
| tree | 98a1120ea97b079a7cf45c15746355f2863f0045 | |
| parent | cb45bf015fd765822a030cffde3853737692dd28 (diff) | |
| download | base-9d2347cf85dd54921725df33a1a77745a770d03e.tar.gz | |
Set lnzipper strategy to local
The execution requirements of the lnzipper expect a filesystem
representation similar to that of the workspace. Other
execution strategies like sandbox or remote use symlinks when building
the action's execution root directory. To have lnzipper correctly build
a ZIP with the proper symlinks, we must use local execution to avoid
archiving sandbox symlinks.
Bug: 185519599
Test: NA
Change-Id: I121ae406079a099ad546489424068c75f1066e9b
| -rw-r--r-- | bazel/common.bazelrc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/bazel/common.bazelrc b/bazel/common.bazelrc index 38caa82866..97d76506d8 100644 --- a/bazel/common.bazelrc +++ b/bazel/common.bazelrc @@ -66,6 +66,10 @@ build --strategy=CppLink=standalone build --strategy=CcStrip=standalone build --stripopt=--strip-unneeded +# lnzipper expects workspace filesystem state (i.e. symlinks) which may not +# be the same when run inside a sandbox or remotely. +build --strategy=lnzipper=local + # Do not register auto-generated cpp toolchains build --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 |