[roll] Roll fuchsia [rbe] Attach unique invocation_id to each action

Then we won't need a reproxy log post-processing step to attach
a build id to each LogRecord.

fuchsia-reproxy-wrap.sh: `build_uuid` is now available even when
auto-uploading metrics+logs is disabled.
Set rewrapper `invocation_id` with a "user:" prefix, so we can know
that the origin was a developer build, as opposed to an infra build.

Original-Bug: b/325521256
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/992517
Original-Revision: 3039a7e3f9a9a84ba657d888d2006139b167e4a4
GitOrigin-RevId: 90af0915b434ad03815c80521787e53504d768b2
Change-Id: I5617b122909dd078868716bd93017679e9483373
1 file changed
tree: b2456feb3e0e375cafd3b7c56796eb0536a6e172
  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.