Maestro promotion failure for AspnetCore repo

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

Aspnetcore repo has had 4 builds in a row fail when publishing packages/symbols in the Maestro Build Promotion pipeline.

##[error].packages\microsoft.dotnet.arcade.sdk\7.0.0-beta.22056.6\tools\SdkTasks\PublishArtifactsInManifest.proj(144,5): error : Sequence contains more than one element 
 at System.Linq.ThrowHelper.ThrowMoreThanOneElementException() 
 at System.Linq.Enumerable.TryGetSingle[TSource](IEnumerable`1 source, Boolean& found) 
 at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source) 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.LookupAsset(String name, Dictionary`2 buildAssets) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 254 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.TryAddAssetLocation(String assetId, String assetVersion, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, LocationType assetLocationType) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 294 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.<>c__DisplayClass171_0.<<PublishAssetsUsingStreamingPublishingAsync>b__0>d.MoveNext() in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1740 
--- End of stack trace from previous location --- 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.PublishAssetsUsingStreamingPublishingAsync(IAssetPublisher assetPublisher, HashSet`1 assetsToPublish, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1712 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.PublishAssetsAsync(IAssetPublisher assetPublisher, HashSet`1 assetsToPublish, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1657 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.HandleBlobPublishingAsync(Dictionary`2 buildAssets, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1038 
 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestV3

Pipelines - https://dev.azure.com/dnceng/internal/_build/results?buildId=1546035&view=logs&j=ba23343f-f710-5af9-782d-5bd26b102304&t=6e277ba4-1c1e-552d-b96f-db0aeb4be20a

[michellemcdaniel]

I think that change should fix it without any changes on our part.

[michellemcdaniel]

I did a little digging: it looks like for some reason assets are being published to BAR multiple times:

Last successful build:

Latest aspnetcore build:

Looking at the MergedManifest.xml for the failed build, each package and blob are listed multiple times:

  <Package Id="Microsoft.JSInterop" Version="7.0.0-alpha.1.22060.28" NonShipping="false" />
  <Package Id="Microsoft.JSInterop" Version="7.0.0-alpha.1.22060.28" NonShipping="false" />
  <Package Id="Microsoft.JSInterop.WebAssembly" Version="7.0.0-alpha.1.22060.28" NonShipping="false" />
  <Package Id="Microsoft.JSInterop.WebAssembly" Version="7.0.0-alpha.1.22060.28" NonShipping="false" />
  <Package Id="Microsoft.SourceBuild.Intermediate.aspnetcore" Version="7.0.0-alpha.1.22060.28" NonShipping="true" />
  <Package Id="RazorPageGenerator" Version="7.0.0-alpha.1.22060.28" NonShipping="true" />
  <Package Id="RazorPageGenerator" Version="7.0.0-alpha.1.22060.28" NonShipping="true" />