| commit | e963ec52d0795cca581a40aa03bf2f17cd1b9b6e | [log] [tgz] |
|---|---|---|
| author | Googler <shahan@google.com> | Sat May 27 05:37:25 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat May 27 05:39:25 2023 -0700 |
| tree | fef12d823aac238fe593e556b55be0b9edbd53d4 | |
| parent | 10fd043243e9df7be026783758cfdb4c67c1ccd9 [diff] |
Add rule-transition to front of ConfiguredTargetFunction Also memoizes computation of TargetAndConfiguration. RELNOTES: As a transitional step in a larger refactoring, rule transitions are applied twice. Once during dependency resolution and once right before analysis of those rules. After the refactoring is complete, rule transitions will be applied only once. Rule transitions are mostly expected to be idempotent, in which case this is a no-op. For transitions where that is not the case, this could be a breaking change or a cause a build performance regression. PiperOrigin-RevId: 535843026 Change-Id: Icfad5a4a84081b7b63ca560ebed97c478cd6e2d4
{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
