Migration: aspire-resourcekit
Migration: aspire-resourcekit
Section titled “Migration: aspire-resourcekit”This repository currently contains a vendored copy of build/PipelineCLI. Migrate it as follows.
- Replace the vendored
build/PipelineCLIwith the sharedPurview.Buildtool pinned to the chosen released version. - Add this
purview-build.json:
{ "Build": { "Solution": "src/ResourceKit.slnx", "TestRoot": "src/tests", "TestPatterns": "*Tests.csproj", "TestFilter": "/*/*/*/*[Category=Unit]" }, "Release": { "Mode": "None" }}- Replace
pr.ymlandrelease.ymlwith thin callers ofpurview-dev/build/.github/workflows/purview-build.ymland.../purview-release.yml, passingbuild-version. Keep the[Category=Unit]filter in the release caller. - In the release caller set
release-mode: NuGetandsecrets: inherit(NUGET_APIKEYandGITHUB_TOKENare read by the shared workflow). - Run the PR pipeline, then delete
build/PipelineCLIand its pipeline-only central package declarations (ModularPipelines*,NuGet.Packaging/Versioning).
The old solution path and unit-test filter are preserved exactly. Other repositories migrate by changing only the JSON paths/patterns; for example dotnet-project-sdk can list unit and integration project globs in Build:TestPatterns.