[roll] Roll fuchsia [build] Begin transition to getting bazel target outputs from a manifest instead of commandline

This starts the transition of using an output-centric
manifest that tells bazel_action.py how to invoke bazel
to generate the outputs.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1470087
Original-Revision: 623b8b544447093191edea10b4cea359227684aa
GitOrigin-RevId: ef5c823df920c18ac33edd4cccb0e969cc276224
Change-Id: Ife4e9e47a4bf1e8cfe2abaa96dfab3e5446ab894
1 file changed
tree: 3f9ad300985c00caeca2cb7e1bcba170bd1762d7
  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.