[roll] Roll fuchsia [bazel] Start the extraction of the implementation of bazel actions to a shareable class This starts the process of moving the common parts of running a bazel task to its own class that can be shared by both gn-target-defined bazel actions and ninja delayed actions. This is a minimal movement of logic around calling bazel and parsing output, so that follow-on CLs can more-readably move individual pieces of logic from one file to another. This CL moves: - The calling of bazel itself - The parsing of output for debug_symbol_manifest_paths - The parsing of error output for missing GN labels This includes one change in behavior: The attribution of any missing GN target dependencies can only done at the level of 'the bazel action', as it won't be possible to know the GN target in question that's missing a dependency as we transition to Ninja delayed Bazel actions. NO_IFTTT=false alarm Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1483218 Original-Revision: 331b4c44cbbf49c8f3a5f28a35edf44f85be0319 GitOrigin-RevId: 007d830bdaeee0ba775a7728c5e955a72aa0dc4a Change-Id: Iac9b9532411dff6cadab992c31d2d7f23bac6486
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.