[roll] Roll fuchsia [bzlmod] Enable bzlmod with Bazel vendor mode

Starting hybrid mode with an empty MODULE.bazel. The vendored
repositories are the bare minimum to run bzlmod.

Vendor directory created with:

fx bazel vendor \
  --vendor_dir=third_party/bazel_vendor \
  --repo=@@platforms \
  --repo=@@rules_license~ \
  --repo=@@bazel_skylib~ \
  --repo=@@rules_java~ \
  --repo=@@rules_python~ \
  --repo=@@bazel_features~ \
  --repo=@@rules_cc~

... then manually create the stub repo, and pin every
repository. This process will later be automated with a script.

Manually created stub repos are:

* apple_support~
* bazel_tools~remote_coverage_tools_extension~remote_coverage_tools

Original-Bug: 414240498, 414246691
OSRB: 414524581

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1258264
Original-Revision: 09ffb8a2ae1c18b99f2830f3876728039feffddc
GitOrigin-RevId: b97a85257c74ad8d42d1a547685feed54381326f
Change-Id: Id652c15599211f818bde33730949560a02e2bf32
1 file changed
tree: fdc3f02a1ce882aa3ce23b522c8b733153f6a7ec
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.