Clean up sandbox stashing directories on Bazel server shutdown. When using --reuse_sandbox_directories, stashed sandbox directories cannot be reused across server instances and were previously left on disk indefinitely when the server shut down or when developers switched workspaces. This led to unbounded disk accumulation over time. Fixes https://github.com/bazelbuild/bazel/issues/27626 RELNOTES: Clean up unused stashed sandbox directories when shutting down the Bazel server. PiperOrigin-RevId: 972583325 Change-Id: I54268307ffa6f0d2bd8371477cd07d90ea959459
{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.
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
