[roll] Roll fuchsia [products][assembly] Make sure bazel assemblies use vendored boards

When a board is shadowed by one in a vendor repo (and used by fx set),
make sure that the bazel product assembly is using the vendored board
configuration input, and not the one in //boards.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/927894
Original-Revision: 56ccd7dbc64210a28cf18dacd54da98bcdea7eec
GitOrigin-RevId: 2cd61e6de8e62cb9a9cecd8e17d873086f8ace18
Change-Id: Ifdcd97c12594a21895a302353bc63c5b7b5f93fe
1 file changed
tree: f2de3d5da54e31ad65fef944c2a8863901245467
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
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 via the IRC channel #fuchsia on Freenode.

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.