| commit | 302971e1b3d803069ac949c0085c0d2a3916c8ab | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Wed Dec 22 07:51:58 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 22 07:53:24 2021 -0800 |
| tree | 441e1b10222c01e82606b71dae053e54e25211a5 | |
| parent | 80ada0f0f8c1ddd44ce559b5534cfbded85c184c [diff] |
Automated rollback of commit 7d09b4a15985052670244c277e4357557b4d0039. *** Reason for rollback *** Now that unknown commit has been submitted, we can roll this forward with a small fix. *** Original change description *** 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: 417820112
{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
