[roll] Roll fuchsia [bazel][updates][tests] Add a dep edge

... attempting to fix a Ninja noop issue.

Depend on Bazel assembly directly to make sure any changes in assembly
(not only image_assembly.json) would trigger a rerun of dir publishing,
otherwise Ninja will fail noop check because depfile of this action
claims files from packages (e.g. hello_world_bin) as inputs.

NOTE: This is not a problem to GN assembly because in Bazel assembly,
the dep relationship between image_assembly.json and the actual assembly
are only expressed in Bazel, not in GN. In GN they are parallel targets
from on bazel_build_group.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1109873
Original-Revision: 19e841b474c42d7125397e9db0f627f9e4cfc58f
GitOrigin-RevId: 959d85a8170a2b7d14a867e89f2a5967dd2706d5
Change-Id: Id6b0d1ede1d4f5a352f36417bff177174434cc94
1 file changed
tree: 3cb48898dfc9a7848f5c87b0d2f97aa3c5dc16a0
  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.