[roll] Roll fuchsia [fdf] Move core DFv2 buildbot target to own file

Move //bundles/buildbot/dfv2:core to //bundles/buildbot/df2/core. A
future CL will remove the old target once it is no longer referenced.

This is to prevent the workstation DFv2 buildbot from failing to build
whenever there are dependency issues with //bundles/buildbot/dfv2:core.
It would fail because the workstation DFv2 buildbot references a target
also found in //bundles/buildbot/dfv2/BUILD.gn and GN would process
all targets in the BUILD file.

Similar CL for the bringup DFv2 buildbot target: fxr/788607

Original-Bug: 120248
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/790642
Original-Revision: 030cc940f86925a241a5518b74e0c3756fea8af2
GitOrigin-RevId: fdca3446191de20070b5d9ff7683f4b827bc25f1
Change-Id: Id4bd8e078c3bd6ce641a4107b36d7fb23c1ef882
1 file changed
tree: 2282e292fe28f340492792f94e93ac697ab56349
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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 via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.