| commit | 6d7557a5bd8052780ddabebdc5d7d3f4d8978251 | [log] [tgz] |
|---|---|---|
| author | ajurkowski <ajurkowski@google.com> | Fri Oct 15 07:48:21 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 15 07:49:47 2021 -0700 |
| tree | 9018fbd38183aad9022782b7b5e4b9791033e27a | |
| parent | 646657fd755076ddd3fc66503badc28d30ce0d5f [diff] |
Switch invocation policy enforcer to use behavior enum instead of the old boolean flags. We have recently added a new enum to express the intended behavior for `SetValue` invocation policy entries. This enum replaces the `overridable` and `append` boolean flags and offers significant advantages over those -- does not have a usable default value, thus must be explicitly set, and does not allow combination of `overridable && append` which is semantically contradictory (`overridable` only applies to non-repetable flags and `append` to repeatable flags). Remove the boolean flags which are now replaced by the new enum and use the enum instead of the boolean flags in invocation policy enforcer. PiperOrigin-RevId: 403372828
{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
