| commit | 72787a1267a6087923aca83bf161f93c0a1323e0 | [log] [tgz] |
|---|---|---|
| author | Philipp Schrader <philipp.schrader@gmail.com> | Tue Aug 09 10:58:49 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 09 11:01:22 2022 -0700 |
| tree | 976354c038bf6d03f7d0041b631e618901ad9f0e | |
| parent | f439f44c782a5d987e28c54fe86f9345deeb956b [diff] |
Refactor Incompatible Target Skipping This patch reworks how Incompatible Target Skipping is implemented. The biggest change is that incompatibility is now checked earlier. This allows us to avoid evaluating dependencies (such as toolchains) in situations where a target is "directly" incompatible. "Direct incompatibility" refers to incompatibility due to a target's `target_compatible_with` value. Moving the incompatibility checking earlier had the undesired effect of visibility restrictions being ignored on incompatible targets. This is tracked in #16044. As per https://github.com/bazelbuild/bazel/pull/14096#issuecomment-1189589626, we will fix it in a separate patch. Fixes #12897. Closes #14096. PiperOrigin-RevId: 466407887 Change-Id: I3014390ddb95c7ff6bfaaf497a32b60c8a6e8fc9
{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
