[roll] Roll fuchsia [bazel][migration] Take dep compleixty into consideration

... when trying to discover next targets to migrate.

From a high-level, complexity to migrate a target equals to the
complexity of this target itself, plus the complexity of all of its
deps that need to be migrated as well.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1491938
Original-Revision: 511f3adcbab8e62102190b046e04ed38b7168e1c
GitOrigin-RevId: 0c87ae5c46db27b21dd1898e6363e81a2c067c09
Change-Id: Icc48984af62218e62642f4ac36eeb7b5dad6295e
1 file changed
tree: 6bde313bce9ce590c924bd5feee38601271463a4
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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.