| commit | 0de7bb95022057e8b89334f44759cf6f950e131f | [log] [tgz] |
|---|---|---|
| author | Oscar Bonilla <6f6231@gmail.com> | Mon Jan 17 03:05:01 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 17 03:06:09 2022 -0800 |
| tree | 9a10c1fa5262a437d52f02b3162923f6cd154e90 | |
| parent | 07812ff95355e3fe07a684dcab596c24a92b8a29 [diff] |
Don't resolve symlinks for --sandbox_base On macOS BigSur, the sandbox-exec command behaves slightly different than on Catalina when firm links are present. Resolving symlinks can prevent the sandbox for allowing write operations to the sandbox base. This effectively reverts a piece of 656a0ba, namely: > When using --experimental_sandbox_base, ensure that symlinks in the path are > resolved. Before this, you had to check whether on your system /dev/shm is a > symlink to /run/shm and then use that instead. Now it no longer matters, as > symlinks are resolved. See https://github.com/bazelbuild/bazel/issues/13766 for full details. Closes #13984. PiperOrigin-RevId: 422319807
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
