[roll] Roll infra/recipes [auto_roller] Don't include dry-run in hash calculation

Don't include whether the current roll is dry-run in the hash
calculation used to generate the Change-Id. This will allow
post_attribution_roller_retrigger builders to retrigger implicitly
dry-run bisector triggered rolls and reuse CQ results.

Original-Bug: b/415692231
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1278484
Original-Revision: 2d03a2201172001d5b22cebd25bcbcaa75f02ebe
GitOrigin-RevId: de9a663fa417ba219db626c2127aad6c3c921ab3
Change-Id: I8629a1cc42aab8a8c0bf806cafb4c3890bfa10f3
1 file changed
tree: c5eceea763220395ebf37a6c7b03a305fbcab171
  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.