| commit | 7978f365ca3216e71e06e51ec78a2cbe61dce8d0 | [log] [tgz] |
|---|---|---|
| author | twigg <twigg@google.com> | Wed Oct 20 14:29:46 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 20 14:30:51 2021 -0700 |
| tree | cf8c77b94dda87584cb0ceaf121341cef8747312 | |
| parent | 101e526116df778a087a60ace0cad4a0f894bdf4 [diff] |
In CTF.K narrow ToolchainContextKey to execution platform Label. Update docs. ConfigurationTargetFunction is very sensitive and should only be completed once per-build for a given Label, BuildConfiguration pair due to performance and correctness (considering unsharable action conflicts in cc rules). Update the documentation of ConfiguredTargetKey to better explain this sensitivity and outline potential pain points. In theory, using the narrower execution platform Label instead of a ToolchainContextKey reduces the chance that two different ConfigurationTargetKey map to the same (Label, BuildConfiguration) leading to the previously mentioned build issues. Thus, concern 3 in the ConfiguredTargetKey is even less likely. In practice, we do not think this issue has actually been observed in a real build. PiperOrigin-RevId: 404639477
{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
