Google Git
Sign in
android / platform / external / bazelbuild-bazel-central-registry / refs/heads/upstream
commit47789036085343a7baa2db17553abcb1d82d7904[log] [tgz]
authorYifan Hong <elsk@google.com>Thu Jan 11 21:58:21 2024 +0000
committerYifan Hong <elsk@google.com>Fri Jan 12 02:04:32 2024 +0000
treeb46384d091464bdf02b9188362aedfd6fe1a1ea7
parenta26099e5ffa366811cb82240881f5bdb7648d1ca [diff]
Add metadata files for bazel-central-registry.

Third-Party Import of: https://github.com/bazelbuild/bazel-central-registry
Request Document: go/android3p
For CL Reviewers: go/android3p#cl-review
For Build Team: go/ab-third-party-imports
Bug: http://b/316187615

Change-Id: I02e8391384a23240d355a6f9bc6c8491d5c54a90
3 files changed
tree: b46384d091464bdf02b9188362aedfd6fe1a1ea7
  1. .bazelci/
  2. .github/
  3. docs/
  4. modules/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. AUTHORS
  10. bazel_registry.json
  11. BUILD
  12. LICENSE
  13. METADATA
  14. metadata.schema.json
  15. MODULE.bazel
  16. MODULE_LICENSE_APACHE2
  17. OWNERS
  18. README.md
  19. WORKSPACE
README.md

Bazel Central Registry

Overview

The default Bazel registry for the Bzlmod external dependency system of Bazel. It is the recommended place to find and publish your favorite Bazel projects. Visit https://registry.bazel.build to check what modules are already available!

Contributing

To contribute, check our BCR policies and contribution guidelines.

Depending on the BCR infrastructure (and how not to)

The core infrastructure of the Bazel Central Registry depends on GitHub and Google Cloud. Bazel users who enable Bzlmod depend on the BCR by default. While we try to keep the BCR infrastructure simple and reliable, we assume no liability for any damages caused by build failures due to potential BCR infrastructure failures.

If you consider it necessary, you can do the following to avoid depending on the BCR infrastructure while still making use of the information checked into the BCR.

  • Clone the BCR repository or mirror the content to your own infrastructure and use the --registry option to change the default Bazel registry to your own.
  • Host your own mirror for all source archive URLs and add the mirror URL in ./bazel_registry.json. You can run bazel run //tools:print_all_src_urls to get the list of source URLs to mirror for all Bazel modules checked into the BCR. For example, https://foo.com/bar.zip should be mirrored to https://<your mirror>/foo.com/bar.zip.