| commit | 217fafe2b492de7349547cc3be2b9eef38628055 | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Thu Oct 12 12:12:01 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 12 12:13:14 2023 -0700 |
| tree | c4cf1e1269f9ebc742ebf41c85304216b0c23aab | |
| parent | 8e2e20f29e5cabbf7236e3d5e56ac005b3dd6ad1 [diff] |
Delete the sandboxfs sandboxing strategy. This change deletes the strategy with the goal of simplifying the codebase. We will focus our effort instead on improving the other sandboxing strategies to make them faster. RELNOTES[INC]: The sandboxfs sandboxing strategy is removed. It hadn't been maintained for a long time, it didn't work for most users and it was not consistently faster while being complex to set up. sandboxfs performance is heavily dependent on the specific setup (setup costs are lower, but you have to pay a penalty for the use of each input) and there are scenarios where it is faster and scenarios where it is slower. Overall it is not worth its weight. PiperOrigin-RevId: 572977096 Change-Id: Idec5ad988bcdcebb4fca48716246d4b1b5ab2984
{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
