[roll] Roll fuchsia [bazel] register debug symbols when building packages

This change builds on a series of previous changes which expose debug
symbols built with bazel to ninja. The package will copy the build-id
directory into ninja land by watching for a newly created build-id stamp
file that contains all of the build ids that were built in the action.
The bazel_action.py script will then look at the build_id directories
that have been moved into the ninja output and copy them to the root
.build-id directory.

If this introduces too many copies we could write an entry into the root
symbol-index.json file that points to the build directory instead.

BUG: b/321081947
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/978553
Original-Revision: 050d085824cf788024e6cba139d7b369acf4f38e
GitOrigin-RevId: 8de478095f9f1425f23135715f53a4142c5d306a
Change-Id: I23972cd8bc99fba808ef90e69dd5a7bf09b5fbf6
1 file changed
tree: ea983342ea3e7fd7069b61486d663662f94494e7
  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.