Skip to content
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

Use CDN urls instead of blob.core.windows.net for downloading runtime/aspnetcore assets #47503

Open
akoeplinger opened this issue Mar 12, 2025 · 0 comments · May be fixed by #47712
Open

Use CDN urls instead of blob.core.windows.net for downloading runtime/aspnetcore assets #47503

akoeplinger opened this issue Mar 12, 2025 · 0 comments · May be fixed by #47712
Assignees
Milestone

Comments

@akoeplinger
Copy link
Member

In #47397 (comment) we noticed that we're downloading directly from dotnetbuilds.blob.core.windows.net and dotnetcli.blob.core.windows.net.

We should be using the CDN urls instead for better performance and in case we ever move storage accounts or can't access them directly anymore.

<InternalBaseURL Condition="$(SYSTEM_TEAMPROJECT) == 'internal'">https://dotnetbuilds.blob.core.windows.net/internal/</InternalBaseURL>
<!-- Base url for official releases. Used to obtain some assets from older releases when necessary. -->
<OfficialBaseURL>https://dotnetcli.blob.core.windows.net/dotnet/</OfficialBaseURL>

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Mar 12, 2025
@Forgind Forgind added the needs team triage Requires a full team discussion label Mar 18, 2025
@marcpopMSFT marcpopMSFT added this to the 10.0.1xx milestone Mar 18, 2025
@marcpopMSFT marcpopMSFT removed untriaged Request triage from a team member needs team triage Requires a full team discussion labels Mar 18, 2025
@Forgind Forgind linked a pull request Mar 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants