| commit | 4ccc21f2f089971e5f4032397764a4be3549c40a | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Tue Jun 14 10:35:57 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 14 10:37:19 2022 -0700 |
| tree | 01c4f0b9a57cfb352660085bc9f98e3483cdec0b | |
| parent | 333d579442a056e721b6b02647a1aa27ffe4f111 [diff] |
Automated rollback of commit 5de967bb27ebdfd31bfa193dc2698cbe46600815. *** Reason for rollback *** Temporarily rolling back until #14852 is fixed. *** Original change description *** Use the proper main repo mapping where appropriate Use the main repo mapping (instead of ALWAYS_FALLBACK) to a) process .bzl load labels in the WORKSPACE file, and b) to process any labels passed to repo rules in either the WORKSPACE file or WORKSPACE-loaded macros. This change only has a noticeable effect for when the workspace name (specified using the `workspace` directive in the WORKSPACE file) is used in labels as `@workspace_name// *** PiperOrigin-RevId: 454899732 Change-Id: Ief9b90f981d3fdb551c53e56e9ffcfdfb9f61bd4
{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
