| commit | ff01f94252a335b2503032a429ffe4c64ba2f3c5 | [log] [tgz] |
|---|---|---|
| author | David Dorwin <ddorwin@fuchsia.infra.roller.google.com> | Mon Nov 11 17:58:12 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 11 10:00:22 2024 -0800 |
| tree | d9cf2303859640a276ae9cc99fa8d04b716c12c9 | |
| parent | 5c4c64c2d9496d607882e62b5159a75260d8245a [diff] |
[roll] Roll fuchsia [developer][build] Increase scope of SDK category marker checks In `ffx_plugin()`, merge the SDK category marker checks into a single higher-level target that depends on the other targets in the template. This also adds coverage that didn't exist before, such as to "//src/developer/ffx/core:lib" via the args target's deps on it. Also make it possible for invokers to have a non-empty `assert_no_deps` list. Similarly, move the check in `fuchsia_controller_internal` up to `fuchsia_controller_py` and add more coverage to `ffx_tool()` and `sdk_python_mobly_test()`. The only marker checks are in `honeydew_no_testonly`, which is already appropriate. Add `visibility` restrictions to some files to make it easier to verify that targets are covered by one of the `assert_no_deps`. Finally, update python templates and `host_test_data()` to pass `assert_no_deps` to more sub-targets. Original-Bug: 314822328 Test: Ensure the checks still work by replacing "//sdk:marker-internal" with "//sdk:marker-partner_internal" in each one at a time and verifying that `fx gen` fails. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1153935 Original-Revision: 0d27afdf3db62bf891953deffc31a1e9c5e5ee92 GitOrigin-RevId: 4380a8f7491fd9acdd73f5c8eab9bc1d91c720a8 Change-Id: I102de11f290ea9bc954b9479d5db148f31b9e1c6
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.