| commit | 7111cbfcecdd3bda3e4beedd8b59dc93d3652607 | [log] [tgz] |
|---|---|---|
| author | hvd <hvd@google.com> | Sat Jan 10 01:04:51 2026 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat Jan 10 01:06:59 2026 -0800 |
| tree | 5897c3724c45561187f149ccd32e61e3c08d91ad | |
| parent | b10a5579ae9b0cfaab6ccfe539a474bfbb0593e6 [diff] |
Automated rollback of commit cecc26b814441f5b7634b42905a0d7be0a321fa8. *** Reason for rollback *** Breaks downstream: - https://buildkite.com/bazel/rules-java-java/builds/3286 - https://buildkite.com/bazel/rules-cc/builds/4524 *** Original change description *** Avoid repo mapping lookup to check builtin restrictions BuiltinRestriction currently accounts for 10-20% of the total CPU time for `bazel build --nobuild //src:bazel`. This is improved by avoiding the repeated creation of "non-visible" `RepositoryName` objects, which trigger a `SpellChecker` computation. Instead, the apparent repo names, which are in fact either module names or legacy WORKSPACE repo names that no longer matter in Bazel 9... PiperOrigin-RevId: 854510657 Change-Id: I3c13b2269c7961583111ec3e20bdd67e141d7277
{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
