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

Plan to disable azureedge.net domains #9676

Open
richlander opened this issue Jan 1, 2025 · 1 comment
Open

Plan to disable azureedge.net domains #9676

richlander opened this issue Jan 1, 2025 · 1 comment

Comments

@richlander
Copy link
Member

richlander commented Jan 1, 2025

We will be disabling use of dotnetcli.azureedge.net and dotnetbuilds.azureedge.net in early 2025. We will start with "scream tests" as early as 2025.02.03 (Feb 3). We will disable domains for ~ one day at a time. We may disable them for longer if we don't hear anything.

At the latest, domains will be permanently disabled on the following dates:

  • 3/31 -- dotnetbuilds.azureedge.net
  • 5/31 -- dotnetcli.azureedge.net

We may disable the domains much sooner.

Test files:

Users should switch to builds.dotnet.microsoft.com and ci.dot.net, respectively, at their earliest convenience. Please email us at [email protected] if this is causing business continuity challenges.

Context: #9671

@dotnet dotnet deleted a comment Jan 4, 2025
@richlander richlander changed the title Disable dotnetcli.azureedge.net and dotnetbuilds.azureedge.net domains Plan to disable azureedge.net domains Jan 24, 2025
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

No branches or pull requests

2 participants
@richlander and others