[roll] Roll fuchsia [archivist] Use configuration capabilities in the integration test

First step leveraging configuration capabilities.

In a follow-up I'll unify this more and remove a bunch of
now-unnecessary components.

I'll also attempt to sub-package the production archivist and
just start it with a different configuration.

Original-Bug: 323187940
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/991052
Original-Revision: 03be6795937a92f349a2ebfae24d26872d5af9ca
GitOrigin-RevId: 9b655c9e35d38a5fa86331eb7184180a7b5c2e45
Change-Id: I5947cb468c0304567d81dbfebe05a51b086e157d
1 file changed
tree: ae360195955728d7a9aae520f15050b2b6040948
  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.