-
Notifications
You must be signed in to change notification settings - Fork 265
Closed
NuGet/NuGet.Client
#5190Labels
Partner:DotNetPriority:2Issues for the current backlog.Issues for the current backlog.Type:Engineeringproduct/infrastructure work/not a customer bug/feature/DCRproduct/infrastructure work/not a customer bug/feature/DCR
Milestone
Description
Contributes to dotnet/source-build#3017
Enable source-build pre-build detection in nuget.client repo, with a custom model of tracking prebuilts. Unlike all other repost that contribute to .NET product, nuget.client does not use Arcade build infra. It is not currently possible to flow .NET dependencies, i.e. SBRP intermediate package. Without package flow, prebuilts can not be eliminated at the point of detection.
Specifics of this work:
- Enable prebuilt detection, ensuring that we only detect prebuilts in inner source-build
- Use baseline exclusion list (https://github.com/NuGet/NuGet.Client/blob/dev/eng/SourceBuildPrebuiltBaseline.xml) to capture all current prebuilts. All exclusions for .NET packages should use
*version. All external packages should use current, static version - Enable
nuget.clientcontributors to communicate any new prebuilts back to source-build team, by documenting the process and/or by leaving a hint in build output of prebuilt detection step - [Optional] Update source-build infra to enable publishing of source-build intermediate package
Process to be followed by repo contributors introducing new prebuilts:
- Follow the upcoming instructions for communicating new prebuilts to source-build team
- Add any new prebuilts to the aforementioned baseline XML, as part of the PR, ensuring source-build leg is clean
mmitche
Metadata
Metadata
Assignees
Labels
Partner:DotNetPriority:2Issues for the current backlog.Issues for the current backlog.Type:Engineeringproduct/infrastructure work/not a customer bug/feature/DCRproduct/infrastructure work/not a customer bug/feature/DCR