| commit | 9eadedb4239a846410ee7f0898cb90b4bae0061b | [log] [tgz] |
|---|---|---|
| author | Googler <kotlaja@google.com> | Tue Mar 14 07:43:46 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 14 07:45:08 2023 -0700 |
| tree | 915adb2ba9336b4018cffcb8453b9b1a5568397d | |
| parent | 49a9502312b6af391a10e1a5c3e05d245ad54899 [diff] |
BEGIN_PUBLIC Deprecate `copy_from_rule` from exec_groups. `test_platform_execgroup_properties_test_inherits_default` test checks if exec_group inherits `exec_compatible_with` from target. Removing `copy_from_rule` we need to specify toolchains and exec constraints directly inside the exec_group. We don't know which constraints the target will set, but those constraints should be relevant only to the rule itself, not to its exec groups. Moreover, seems like this inheritance from target to exec groups is not been used in practice. RELNOTES[INC]: `copy_from_rule` is exec_groups is deprecated (https://github.com/bazelbuild/bazel/issues/17668). END_PUBLIC PiperOrigin-RevId: 516521869 Change-Id: I9ac998783e7ccd2ecac53122a21a159c59255816
{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
