[roll] Roll infra/recipes [artifacts] Always emit artifacts_gcs_bucket prop

...no matter which recipe is calling into
`api.artifacts.upload_from_manifest()`, so this property will now be
emitted by the `[bazel_]build_test_upload` recipes in addition to the
fuchsia recipes.

As a side benefit, we can remove a line of logic from the `fuchsia`
recipe module that I've been trying to trim down since it contains
only miscellaneous common logic that doesn't belong anywhere else. Then
to ensure that parent builds, in addition to subbuilds, continue to emit
the property, fuchsia.py must copy the property from the subbuild.

Original-Fixed: 118846
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/786723
Original-Revision: 6a6c982a6456078821955945c6f64e4afd61480a
GitOrigin-RevId: e179bbfa09b82c89e149d3da64dbafc6bbddcd29
Change-Id: Iad073702cd8977bce10e34897bdb82ad4a054f4a
1 file changed
tree: c40483ed9e4acde2ec787056eb1055047ec34c8b
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.