| commit | f29405c5356bd797727fcd50cea9fcc8caead76c | [log] [tgz] |
|---|---|---|
| author | Googler <jingwen@google.com> | Wed Apr 03 00:25:06 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 03 00:26:58 2024 -0700 |
| tree | dfa10fca8b86cb1d403c52b0c4380c0dbac8a225 | |
| parent | 12de6fb460436aa7f873da203b8803d2190e965b [diff] |
skyfocus: move callsite from `SkyfocusModule#onBuildToolFinalizingEvent` to `BuildTool#processRequest`, and remove `SkyfocusModule` as an EventBus listener. This gets rid of the "effects at a distance", and makes reasoning about the Skyfocus lifecycle simpler. The associated `BuildToolFinalizingEvent` is no longer needed, and `SkyfocusModule` is moved to the `runtime` package since it deals with runtime classes. More specifically, any `AbruptExitException` thrown during Skyfocus will now be handled appropriately by the `BuildTool` crash management, and not actually crash Blaze server when it was called from an EventBus subscriber. Also remove the `CommandEnvironment` member from `SkyfocusModule`. PiperOrigin-RevId: 621427034 Change-Id: Id0de1a4a09b80bc8a9599043ca34aba1ff7e38c5
{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
