commit | 7d09b4a15985052670244c277e4357557b4d0039 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Tue Dec 21 12:16:45 2021 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 21 12:17:56 2021 -0800 |
tree | 2b8000c0a3a5b8f13a8d21108ed6b0a585ceecf1 | |
parent | fafe16ddafc5c720ad810eed149dd6a04581a232 [diff] |
Automated rollback of commit 13112c027c0064cf0a29256e80560cb6630af94d. *** Reason for rollback *** Causes [failures](https://buildkite.com/bazel/google-bazel-presubmit/builds/52620) in Presubmit of unknown commit, itself a Rollback of https://github.com/bazelbuild/bazel/commit/78d01316b22667e9d1758472c91dfee35cc189bd *** Original change description *** Bzlmod: When evaluating extensions in the main repo, do not load WORKSPACE (https://github.com/bazelbuild/bazel/issues/13316) See new comment in BzlLoadFunction.java for details. https://github.com/bazelbuild/bazel-central-registry/pull/47#issuecomment-998883652 also has a bit more context. PiperOrigin-RevId: 417668153
{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