[roll] Roll infra/recipes [auto_roller] Assume dry_run is True for shadow builds

If the roller is being run from a shadow bucket, assume dry_run is True.
This means all led-triggered rollers will be dry runs. Some shadow
builds run as service accounts that don't have permission to vote
Bot-Commit+1 or Commit-Queue+2, and this enables led testing of those
rollers.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1088909
Original-Revision: e9fdaa1e09641fa2f2218d3a1f9cf558441fcec1
GitOrigin-RevId: d07907264014eb9483b2d0e147794a9591edbf0c
Change-Id: I116f4954f95a56e9f78d06d099310e3123205252
1 file changed
tree: 8942d590ec7d2425ce776b6ff914a0bc596a1e90
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.