| commit | 5a6b1a85e82f4b034cc2e96fdc84c0c3c0b5571a | [log] [tgz] |
|---|---|---|
| author | kotlaja <kotlaja@google.com> | Tue May 03 05:38:25 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 03 05:40:14 2022 -0700 |
| tree | 220231d02f994e4d2d9bf1be8ae8e0a8b1c22276 | |
| parent | b2cbc9a17c90f9ddeb88eca4756cb2fc764abebe [diff] |
Automated rollback of commit ae349e9368f90bc5cf27f51ecc773ada9e3a514c. *** Reason for rollback *** This CL breaks proto_common.bzl file which seems that can't load providers.bzl file. *** Original change description *** Export ProtoLangToolchainInfo provider and flip proto_lang_toolchain rule I’ve exported ProtoLangToolchainInfo provider from it’s native class by adding two new functions: one that’s creating starlark provider (create function), and the other that’s wrapping the starlark provider as a native one (get function). Also, in all locations where native ProtoLangToolchainInfo provider was used/created, I’ve modified it with previously mentioned functions. I’ve also replaced native ProtoL... *** PiperOrigin-RevId: 446171449
{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
