| commit | 2cdb6470af1a5cca2c1b58f0ae6dbd6a4840310f | [log] [tgz] |
|---|---|---|
| author | jhorvitz <jhorvitz@google.com> | Wed Oct 06 14:22:36 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 06 14:23:53 2021 -0700 |
| tree | 79ba99169c5bfb18f67789bb85dbd709b022a40f | |
| parent | cb1fb6ebb09e2a5930e652b4371d656410bc8edd [diff] |
Reduce parameters in `RuleContext` and its builder in favor of using enclosing objects `AnalysisEnvironment` and `ConfiguredRuleClassProvider`. Inspired by `TODO(bazel-team): I get the feeling we could delete much of the boilerplate by replacing some of these fields with a RuleClassProvider -- both in the builder and in the RuleContext itself.` (written by brandjon@). I'm working on a change that will need yet another `ConfiguredRuleClassProvider` field in `RuleContext`, so this will be helpful. Reduce `RuleContext.Builder` constructor parameters to only those that are needed up-front. PiperOrigin-RevId: 401338523
{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
