| commit | 0253bde3abbe2bd19508435362ed3e9ac91bdc92 | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Wed Feb 14 10:06:45 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 14 10:07:57 2024 -0800 |
| tree | f77d340f435a1339bdf7426c9a50eeac55432457 | |
| parent | 8aedcc4b36f3b5d534263d33e15de6a5cff076d3 [diff] |
Move sandbox_stash to sandboxBase from outputBase Because the sandbox_base can be set via the configuration flag `--sandbox_base`, it might be that the stashes end up in a different filesystem than the actual sandbox, which makes `reuse_sandbox_directories` inefficient. Apart from making sure that the stash is under `sandboxBase`, this change refactors the logic about which directories to delete from `sandboxBase` and when. The stash will persist between incremental builds but after a bazel server restart it will be deleted. This change also refactors the tests since we had three different tests which weren't testing anything different. The change also includes more profiling spans related to reuse_sandbox_directories. Works towards fixing #20965. PiperOrigin-RevId: 607023622 Change-Id: I59f9d2066e966dd60dd11f7d82815d0c89f2ce23
{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
