-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/3.0] Switch to embedded package icon #14394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Same as dotnet/razor#1166 (comment). Maybe this is only happening in jobs that build packages by default? @dougbu should we just update to the GA SDK? All the repos are currently on |
@dougbu Arcade will force the update, but feel free to get ahead of it. FYI please update branding to 3.0.1 and turn off stable builds prior to checking anything else into 3.0 |
Just updated to the GA SDK |
Code Check:
|
Lots of builds failing with:
Seeing this in |
Ah, I think the issue is that these 2 projects are using old versions of nuget: The one in RepoTasks is probably safe to upgrade, but it looks like the issue referenced in GenerateNugetPackageWithMsi.ps1 is still active: NuGet/Home#5016. @dougbu bumping the nuget version there seems likely to increase the build time (possibly significantly), can you suggest a different workaround? Will push a commit now to update these versions, as a test. |
The "Build Installers" step in x64/x86 build is the one to keep an eye on, it might become significantly slower |
Errors so far are about the build machines not having MSBuild 16.3 😞 |
W.r.t NuGet/Home#5016 isn't that problem specific to cases involving |
Going to try using a preview9 SDK as a temporary workaround - hopefully there is a window between when |
Hitting the |
Can't use the preview9 SDK - will revert back to the GA one |
/azp run AspNetCore-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run AspNetCore-helix-test |
Azure Pipelines successfully started running 1 pipeline(s). |
Contributes to aspnet/AspNetCore-Internal#3103