| commit | e812374c01f6f1795e61818cd027973a03bfb7db | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Tue Jul 15 11:56:15 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 15 11:57:25 2025 -0700 |
| tree | 012d5d38d80d4d56c86164eaab9943efc77dc8c2 | |
| parent | 7ea80bd9258785ad932c8a67270cd7cc957cf0a7 [diff] |
Remove repo-related code from `Package` and co. Repo rule logic is now completely decoupled from build rule logic. Time to delete some code! - `Package`s can no longer be "repo rule packages". All related logic is deleted. - In particular, `Package#getSourceRoot` returns a `Root` instead of an `Optional<Root>`. - `RuleClass` can no longer be of type `WORKSPACE`. - `TargetDefinitionContext#fromOrFail` and friends have all mention of `WORKSPACE` scrubbed. Fixes #26131. PiperOrigin-RevId: 783419143 Change-Id: Ibb3d1988b1c62b5cd6c8ea9137b5ccacc58db489
{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
