| commit | 8b7f40813c02ade259731694417ff13a862ce0a8 | [log] [tgz] |
|---|---|---|
| author | Googler <brandjon@google.com> | Mon Aug 19 07:35:11 2024 -0700 |
| committer | keertk <keerthanakumar@google.com> | Thu Aug 22 18:02:42 2024 +0000 |
| tree | 3b4873cd40ee2e29c830e0a837e0a03b506cf682 | |
| parent | ffdf41acfd4d82bdfd3f855b8f4aa3840d918eba [diff] |
Automated rollback of commit 618dd78383ebea9f656c144aeef72345999c90e3. *** Reason for rollback *** Breaks nightly (b/360823207) *** Original change description *** Change some configuration-independent deps from exec config to "no config". Specifically: - deps on `package_metadata` and `applicable_licenses` attributes (common to all rules). These deps are for license metadata rules consumed by https://github.com/bazelbuild/rules_license. They don't create build actions and don't need to be configured. - deps on `compatible_with` and `restricted_to` attributes (also common to all rules). These are part of a deprecated constraints resolution framework, a... PiperOrigin-RevId: 664801185 Change-Id: I709f091dc6c02f98b8d11e953e0dbc7a5203480a
{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
