| commit | ef758fa57c31ed7c04937c3b4a263a0e25315bc2 | [log] [tgz] |
|---|---|---|
| author | Googler <yuyueny@google.com> | Mon Dec 18 09:13:50 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 18 09:15:22 2023 -0800 |
| tree | 04a77d22d9a7be158590c1b709c6acf05cbc2c0d | |
| parent | aa1e0b431f1eac8acb359e5e13b1a209f8c2e246 [diff] |
Automated rollback of commit 07eb2d77f94f9e11e64082dab9581ad7acf44dc7. *** Reason for rollback *** Re-fix the `subpackages()` bug when considering a corner case In the initial change, we have introduced another bug: Consider computing `subpackages(["sub/**"])` while `sub/BUILD` exists, we should return "sub", which is the behavior of file/directory glob matching. However, the initial fix returns EMPTY in this case. This change also adds more test coverage for calling `subpackages(["sub/**"])` when `sub` is a subpackage. PiperOrigin-RevId: 591917000 Change-Id: Iab41cc59b0da7f7794a90cd10aaac8900ee0d79b
{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
