[roll] Roll fuchsia [bazel] Consolidate logic for telling Bazel to output debug symbol file manifests to implementation class This re-consolidates the logic around telling Bazel to produce the debug symbol manifests to its DEBUG output, and the filtering-out of those output lines so that they don't clutter up the stdout of the build to the BazelAction class. This was split up by the desire to keep the stdout processing with the invocation of Bazel while also not moving all the cmd_args generation at the same time, so that individual feature moves are easier to see and track in individual CLs. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1483256 Original-Revision: b29674caa4b95dd064b60dd409ae7478d17e110f GitOrigin-RevId: f00dc124c70c3ebd59ba603e3d2ff58653dfec09 Change-Id: I17dff7820c5d0f3d384d031c392b2e8bd0ab66e3
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.