commit | 6181a3cc69e1bd5fa564687d755545bd86bf6110 | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Thu Oct 28 03:11:19 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 28 03:12:46 2021 -0700 |
tree | 39a8dd434d374e9ca27ed81e89e4d5a62c315d0a | |
parent | d422c8705e2a6d5709ec016752c27f439cc53357 [diff] |
Enable Bzlmod for Bazel Bazel can now be built with Bzlmod with dependencies fetched from [the Bazel Central Registry](https://github.com/bazelbuild/bazel-central-registry) (https://github.com/bazelbuild/bazel-central-registry/issues/7). Changes in this PR: - Added MODULE.bazel file for Bazel - Added MODULE.bazel file for third_party/remoteapis and third_party/googleapis to make them work as Bazel modules - Updated gson to 2.8.6, because we build with protobuf 3.19.0 with Bzlmod which needs a newer version of gson. - Added WORKSPACE.bzlmod, this eventually should be empty, but for now we still need some bind rules to make some jar dependencies available for protobuf. - package-bazel.sh: use wildcard to locate the directory of the platforms repo, whose canonical repo name is `platform.<version>` when building with Bzlmod. To build Bazel with Bzlmod: - Copy WORKSPACE.bzlmod to WORKSPACE - Run `USE_BAZEL_VERSION=last_green bazelisk build --experimental_enable_bzlmod //src:bazel_nojdk` Closes #14171. PiperOrigin-RevId: 406097216
{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