| commit | 49850f89f86ab25d32a163fc5e032c4abec45549 | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Thu Apr 25 15:45:01 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 25 15:46:46 2024 -0700 |
| tree | 61652e3f6130b98b8cb6a9ec23ea9003cca45d50 | |
| parent | 7ffa32547eff706f4e54883874a8ff25c8af2883 [diff] |
Replace most Bzlmod events with a Skyframe graph lookup Retaining `Postable`s across the graph increases the memory usage of every dependent Skyframe node. `ModuleExtensionResolutionEvent` is replaced with a lookup of the "done" Skyframe nodes for extension evaluation in `BazelLockFileModule#afterCommand`. `RootModuleFileFixupEvent` is replaced with direct storage in `SingleExtensionEvalValue`. The validation of repos imported from an extension is moved into a separate `SkyFunction`. This simplifies `bazel mod tidy`, which no longer needs to swallow certain exceptions, and allows cache hits when only the (invalid) imports of an extension are modified even without the lockfile. The `BazelModuleResolutionEvent` is kept for now, but will become obsolete with the new lockfile format. Work towards #20369 Closes #22058. PiperOrigin-RevId: 628213907 Change-Id: I8ba19f5151a8183be5051c8d9280f93476db2272
{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
