[roll] Roll fuchsia [bazel] Use fuchsia_platform for //build/bazel/rules/tests Specify the Bazel platform "fuchsia_platform_<CPU>" for the Bazel actions in //build/bazel/rules/tests. Now that we have a sysroot independent from the Bazel SDK, we can use the proper platform to build Fuchsia platform targets and remove the dependency on the Bazel SDK. To enable this, allow `bazel_action()`'s `bazel_platform` platform to be used with non-host actions. The `api_level_and_cpu_combinations_transition` no longer supports the "fuchsia" Bazel platform. Thus, building targets that use it directly with that platform now fails. For example, `fx bazel build --config=fuchsia //build/bazel/rules/tests:quick_tests` is no longer supported. Original-Original-Bug: 505802054 Test: `fx clean && fx build //build/bazel/rules/tests:tests` succeeds and does not build 10,000+ GN targets for the IDK. Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1631846 Original-Original-Revision: 472fda03f1664dd3422a2f6c2d3337e29a604fcf GitOrigin-RevId: 194aae2ecf5a24b50b31f0c713e0348861a59728 Change-Id: I30ac34b946253d8292186812d9e176eb9121c7f8 Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1635794 Cr-Commit-Position: refs/heads/main@{#193880}
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.