commit | 0b069c975c27bda50683759eb19ea49d3f0d904e | [log] [tgz] |
---|---|---|
author | ilist <ilist@google.com> | Tue Sep 14 06:41:16 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 14 06:42:25 2021 -0700 |
tree | 69f0b5ba5173c1a14da1b41b0898dc65a183b5d6 | |
parent | d1532aef9a39a535c0dba73e445a1d05e39297bb [diff] |
Automated rollback of commit f2efbb718aec0a6b47eefc65362205548b33e5a7. *** Reason for rollback *** Giving too much access to Starlark rules which leads to additional complexity. *** Original change description *** Expose rule kind on Starlark rule context attributes. The rule kind is needed to implement some checks when porting the rules to Starlark. The value of a rule kind can already be inspected using an aspect via target.kind, this is just providing a more direct access from the rule implementation. PiperOrigin-RevId: 396584163
{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