[roll] Roll infra/recipes [auto_roller] Include task service account in hash

Include the task service account in the data used to compute the
Change-Id. This minimizes conflicts when the task service account is
changed but the builder stays the same. The new task SA likely won't
have permission to restore/update/abandon a roll CL owned by the
previous task SA.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/890754
Presubmit-Verified: CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: 19e4667dfa27b592f4dfff17b28aa514d50bd9f3
GitOrigin-RevId: dc47108693ec165f99d55a8fa88d2533a5dc28a4
Change-Id: Ic9a71a135552251e8234ce4347f1643d316bb3ce
1 file changed
tree: b8b817cec777256c640c4d0a38b898f976ed8df5
  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.