Move information whether the build is using in-memory action file system from `ActionExecutedEvent` to `BuildStartingEvent`. A build will either use in-memory file system for all actions or none. Move the indicator for this from `ActionExecutedEvent` to `BuildStartingEvent` so that subscibers can note that information when execution starts and use it when receiving events. This way, we can take advantage of this information for other kinds of events. PiperOrigin-RevId: 453749440 Change-Id: I15dfab0a4af492cbd847dab419f3e13508a2556f
{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
