| commit | 6fba6fdf8cb9cb953bbe32d324c9a2fe51780b35 | [log] [tgz] |
|---|---|---|
| author | messa <messa@google.com> | Wed Sep 17 12:20:39 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 17 12:21:55 2025 -0700 |
| tree | fd7c79de225e9b160c76dfb06050c923011f8c8c | |
| parent | b0b5497749eb1550c96d92c52f477689e07dca6f [diff] |
Rollforward of https://github.com/bazelbuild/bazel/commit/d96e067331680dd4dec9fb391ed148d90daafbf8 after addressing the performance regression. This change introduces a cache for the starlark transitions' build settings. This is because even if a transition value is evaluated and cached, the [`TransitionApplier`](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/analysis/producers/TransitionApplier.java#L95-L101) computes the starlark build settings involved with the transition multiple times before checking the transition cache. This causes `StarlarkTransition.java#addLabelIfRelevant` to be more expensive specifically for the execution transition because it is called too many times checking almost all native flags to find if any of them is an alias of a starlark flag. The logic for computing the starlark build settings of a transition is moved to `StarlarkTransitionCache` to only be evaluated if the value is not already cached. During a single analysis, the value of `--flag_alias` should not change and hence we can cache the starlark build settings based only on the transition. After analysis phase, this cache is cleared with the transitions cache to ensure reevaluation in following builds with possibly different `--flag_alias` values. PiperOrigin-RevId: 808250144 Change-Id: I00595d7c9e54f122d81f407a28cf6b870142fb6c
{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
