[roll] Roll fuchsia [paver] Remove AbrClientFactory

Always build ABR clients out of a DevicePartitioner.  There's a few
reasons for this:

- Some ABR clients (e.g. Kola) rely on a partitioner existing.
- In storage-host configurations, I plan to scope BlockDevices to
  partitions published by a specific storage-host instance, and tie a
  DevicePartitioner to that BlockDevices instance.  This means we need
  to create a DevicePartitioner before creating an ABR client anyways,
  if we want them to look at the same set of partitions.
- It's tidier this way; we only need one registry and can't accidentally
  create the wrong ABR client.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1152573
Original-Revision: 3c691581541b5452dbd3e44a725919135aee6e60
GitOrigin-RevId: 7859c21548958befdb1de42fcc68b605886d28f2
Change-Id: Ib6428472dfe514369717f07f32519b43f6e99f96
1 file changed
tree: df7f148cf916466f49739668c1c778d072096504
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 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.