-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Backport Use CDN for .NET Assets to release 6.0 #39043
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
|
Hi @TanayParikh. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
|
To confirm: There's no CDN for the 6.0 bits❔ |
There are two storage accounts, dotnetcli and dotnetbuilds. Both have CDNs, but the container structure is different and this may be the source of confusion. I may have been incorrect about the inflection point because I saw 6.0* blobs on the dotnetbuilds account, but in general if you are going to use them at scale the CDN is the right choice. e.g. https://dotnetbuilds.azureedge.net/public/Runtime/6.0.0-rtm.21522.10/dotnet-runtime-6.0.0-linux-arm.tar.gz doesn't exist, but https://dotnetcli.azureedge.net/dotnet/Runtime/6.0.0-rtm.21522.10/dotnet-runtime-6.0.0-linux-arm.tar.gz does and uses a CDN. |
|
Hi @MattGal. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@dotnet/aspnet-build requesting merge please. |
#39007