Skip to content

[maint/maint-67] Update dependencies from dotnet/arcade - #98

Merged
dotnet-maestro[bot] merged 1 commit into
maint/maint-67from
darc-maint/maint-67-9d854d66-d97e-4c8d-9653-1b6db6b96d98
Apr 5, 2021
Merged

[maint/maint-67] Update dependencies from dotnet/arcade#98
dotnet-maestro[bot] merged 1 commit into
maint/maint-67from
darc-maint/maint-67-9d854d66-d97e-4c8d-9653-1b6db6b96d98

Conversation

@dotnet-maestro

@dotnet-maestro dotnet-maestro Bot commented Apr 5, 2021

Copy link
Copy Markdown

This pull request updates the following dependencies

From https://github.com/dotnet/arcade

  • Subscription: d28e6cfd-b630-408a-d2d3-08d82368e557
  • Build: 20210403.1
  • Date Produced: 4/3/2021 9:50 AM
  • Commit: 1bfe91238cb39b9620b878b8f1bf0c789324b4cd
  • Branch: refs/heads/main

…403.1

Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk
 From Version 6.0.0-beta.21176.2 -> To Version 6.0.0-beta.21203.1
@dotnet-maestro
dotnet-maestro Bot merged commit 8d8a9f4 into maint/maint-67 Apr 5, 2021
@dotnet-maestro
dotnet-maestro Bot deleted the darc-maint/maint-67-9d854d66-d97e-4c8d-9653-1b6db6b96d98 branch April 5, 2021 12:33
directhex pushed a commit that referenced this pull request May 13, 2022
Since the Nuget creation and Nuget code signing are now done as two separate stages in the build pipeline, the Windows symbols publishing task fails as it relied on the DownloadBuildArtifacts tasks in the Nuget creation step. (This was missed in the refactoring of the pipeline in PR #93.)
However, since the Nuget doesn't contain any symbols at all, we can move the DownloadBuildArtifacts tasks entirely to the Nuget code signing stage instead.

Also, it turns out that the PublishSymbols task cannot run on the public Azure Pipelines pool and must be run on the PackageES pool. (Note: I skipped the actual publish step when testing PR #93, as you can't unpublish things once published. However, when running the Release Pipeline to publish for real, it errors out.)

Note: FWIW, the ProjectReunion pipeline also uses the PackageES lab for publishing symbols as well here:
https://github.com/microsoft/ProjectReunion/blob/1714557cad5e740c0153e451fbf0311c8e5bdfc1/build/ProjectReunion-BuildFoundation.yml#L172-L188
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants