[roll] Roll fuchsia [assembly][bazel] Prebuilt configs can be found in nested dirs There are some situations where the assembly artifact that was uploaded to CIPD was nested in a directory. The prebuilt bazel rules can now find the correct directory inside by looking for the config json inside. This lets us pass the top-level CIPD package to the bazel rules, and trust the rules to find the right assembly container directory. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1239633 Original-Revision: e5902b5f0b79a1b853eb44d4e70c5697a5116e49 GitOrigin-RevId: f1f5f7320b6eda718673b92e7406987d2e989348 Change-Id: I62156fef767276b0f5d91618753aaadbd4e2bf80
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.