[QCR][Release ring]Release day pipeline should push private transport packages to public feeds on release day

• This issue is blocking
• This issue is causing unreasonable pain

For an internal build, release day stage of the pipeline, in concert with the push to nuget.org, should take internal transport packages and push them to public feeds so that branding update PRs can complete in public.

It’s is not necessary to know whether a build is public or private. Just look for packages that exist on internal transport feeds and push them to the corresponding public feeds. Here is a powershell snippet sample which will do this:

builds = Get-Content \\vsufile\patches\sign\NET\CORE_BUILDS\3.1.X\3.1.4\3.1.300-servicing-015161\manifest.json | ConvertFrom-Json;

foreach ($asset in $builds.builds.assets) {
  if ($asset.Source.StartsWith('https://pkgs.dev.azure.com/dnceng/_apis/packaging/feeds/dotnet3.1-internal-transport')) {
    D:\tools\nuget.exe push -Source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet3.1-transport/nuget/v3/index.json" -ApiKey AzureDevOps $asset.targets[0] -SkipDuplicate
  } 
}

Feed: mapping:

• dotnet3.1-internal-transport -> dotnet3.1-transport
• dotnet5-internal-transport -> dotnet5-transport

[michellemcdaniel]

Yes. I’m trying to make this as general as possible.

[michellemcdaniel]

Do the symbols also need to be moved? So:

dotnet5-internal-symbols -> dotnet5-symbols