| commit | e060edfdd7ad08ee381b18cc3a5f65719639cde0 | [log] [tgz] |
|---|---|---|
| author | leba <leba@google.com> | Mon Apr 25 06:52:44 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 25 06:54:24 2022 -0700 |
| tree | bd4e5d386c9d2b018ee70fa263c3018eae73e4e7 | |
| parent | 46e0be4ef67901cab7896348c89de06396f737b4 [diff] |
Use an event-based system to collect analyzed/built targets/tests/aspects. This change puts in place the necessary classes for such a system, and apply said system to Skymeld (also experimental). A follow-up change will introduce this to the regular code path, guarded behind a flag. There are basically 5 events: - target analyzed - test analyzed - aspect analyzed - target built - aspect built Each event is posted at most once. For Skymeld, the posting takes place from within a SkyFunction, that means we need to prevent posting multiple times when 1) the function restarts (with the use of State) and 2) error bubbling (by checking with the environment if we're in error bubbling). Also changed the various calls to eventBus.post(...) in SkyFunctions to instead use env.getListener().post(...), which is a more canonical way to post events from Skyframe. PiperOrigin-RevId: 444256098
{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
