[roll] Roll infra/recipes [fuchsia_roller] Also update corresponding submodules

Now that we have Jiri manifests in fuchsia.git, we should update all the
rollers into fuchsia.git to also update the corresponding submodule when
rolling. This will reduce the number of submodule-update commits that
clutter the fuchsia log.

We'll still need to keep submodule-update around but it will only run
after manual rolls, or rolls of the few remaining repositories (cobalt,
cobalt-config, and antlion) that are still pinned in integration.git
instead of fuchsia.git.

Test: https://fxrev.dev/1288532

Original-Fixed: 421230590
Depends-on: I3c8d273a641edb25b98a149ade4658faf55fda42
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1288724
Dependencies-Satisfied: CL Deps Checker <cl-deps-checker@fuchsia-internal-service-accts.iam.gserviceaccount.com>
Original-Revision: 948c1a36dc7532de21ffcf740ebcf435ccf4b4a2
GitOrigin-RevId: 0f77b33c8b6c3d1b837594f1f9bb347fbcff984c
Change-Id: I0c5e290bee020cbd6dbd062724e73ad092241d5e
1 file changed
tree: 3ecc9d478166746504de86a23a55e1fe7c30f608
  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.