[roll] Roll infra/recipes [fuchsia/fuchsia] Do not upload to catapult for bisector builds.

Builds launched by the bisector builder will be out of order, as in
they'll be run on older commits. This causes out-of-order uploads to
catapult which aren't handled properly so we shouldn't upload to
catapult in this case.

Original-Bug: 445994940
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1372718
Original-Revision: 38c8f0eb21cfd9e86efebe4cd8a670acae94eb84
GitOrigin-RevId: c4c8d8544cbe05def06cd3dfce1447c05082b58a
Change-Id: I58c7ac34f25211f4563b6fe79de6f88e599f1a88
1 file changed
tree: f5e17edbe207e4aa260d14454353fc0e4f7d2ea1
  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.