commit | 59718efc01c412cba27a75db693ca2050f9ac1f3 | [log] [tgz] |
---|---|---|
author | Fabian Meumertzheim <fabian@meumertzhe.im> | Fri May 03 12:41:19 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri May 03 12:43:02 2024 -0700 |
tree | c7e267ce8fdfd0258002039d35831e296b913727 | |
parent | e60b8fb5f698e6566b85ce0ec01cab9a818c68a0 [diff] |
Avoid Windows short paths in Bzlmod When a `PathFragment` is created on Windows and one of its segments looks like a Windows short path, additional file I/O is performed to resolve it to its long form. Certain Bzlmod-managed repository names could look like such paths, which potentially slows down analysis. Instead, prepend a `v` to the version of multi-version modules to avoid this. Requires bumping the lockfile version as canonical label literals may be embedded in lockfiles. Closes #22219. PiperOrigin-RevId: 630468932 Change-Id: I54d58ac23e779cda50301301f16109db27d11306
{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