commit | 5cf60bdd4c94f8078736e064f531082d72be57fe | [log] [tgz] |
---|---|---|
author | Googler <yuyueny@google.com> | Wed May 01 16:07:26 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed May 01 16:09:12 2024 -0700 |
tree | 7f64aaa86583b66c027209b1ab94954318c71ce5 | |
parent | 43fdcd36f88a3f3a549cecc3f69627537734bb14 [diff] |
Implement `PackageFunctionWithSingleGlobsDep` so that `PackageFunction` relies on a single GLOBS node This change adds a new `PackageFunctionWithSingleGlobsDep` class which creates a single GLOBS node to evaluate all package `BUILD` file's glob expression. Bazel adopts this new type of `PackageFunction` so that the number of nodes rdeping on PACKAGE is significantly reduced. In order to facilitate readability, globbing strategies are renamed to `MULTIPLE_GLOB_HYBRID` (former `SKYFRAME_HYBRID`) and `SINGLE_GLOBS_HYBRID`. The heuristic node dropping logic is also refactored so that PACKAGE dep GLOBS node are removed after PACKAGE evaluation completes. PiperOrigin-RevId: 629867325 Change-Id: I97c5aa71dc6adc155a1d32adb39c3812877768ba
{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