[roll] Roll fuchsia [bazel] Write bazel_action() Bazel invocation to file.

To help debug Bazel invocations from Ninja, ensure that bazel_action.py
writes a file with the exact Bazel invocation command that it launches,
and expose it through a new bazel_command_file metadata key for the
out/default/bazel_build_action_targets.json file.

This also exposes the profile and mapping paths.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1245064
Original-Revision: a095f18ea3c39f7068f5c9770ea3dcce0689d29f
GitOrigin-RevId: 39289aefc2202fe8bb88e52e518394f4ee42f96d
Change-Id: Ic04593ad285313d56182b605c4c39a83f800431c
1 file changed
tree: 7a14edac1c4fcf1f57c57552543f25c06da0679e
  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 in one of the communication channels documented at get involved.

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.