[roll] Roll infra/recipes [rust_stage0_trigger] Change the revision sent to the next stage builders

We use 'next_stage_builders' argument to trigger a prod stage0 build
from CI. By default, it passed the stage0 revision of the current
revision. This caused an issue for the prod build as it will also
look up the stage0 revision of the revision sent from the input
property, and it won't match the one used in the CI. This patch
fixed this issue.

Original-Original-Bug: 491276197
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1640095
Original-Original-Revision: 92366fdcfe09c512fbdf18872b94e44f7f39582e
GitOrigin-RevId: f71865010af64a835a6f24d0e1331e0a25577938
Change-Id: Ia303c9f0cb24eb64a3e9eee27a7098d92d401c25
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1640108
Cr-Commit-Position: refs/heads/main@{#194177}
1 file changed
tree: adcfec108fede8ae1d7fc8224aca33d90570aea4
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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.