[roll] Roll infra/recipes [fwdr] jiri update after updating manifests

The `update_3p_packages` logic is affected by what version of the Dart
SDK is in use, so for it to be consistent we must `jiri update` to
ensure we download the newly pinned version of the Dart SDK after an
update.

Example failure: https://ci.chromium.org/b/8777752652019056705

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/873736
Presubmit-Verified: CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: 996acbe77e79e9885b18052c9fd3c1798e3645e9
GitOrigin-RevId: bd7d37346f550e48c5b6e8af3ae3ddb37722a360
Change-Id: Iccf7ccf0747bf159e4c074e3a19417b8f3d84c6e
1 file changed
tree: f80f865dcf59afb37520ae9845b966f453c99bf9
  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.