-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
This was referenced Jan 24, 2025
https://dotnetbuilds.azureedge.net/ was disabled at the Traffic Manager level. |
Venkad000
pushed a commit
to Venkad000/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment)
Venkad000
pushed a commit
to Venkad000/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment) Signed-off-by: Venkad Krishna C <[email protected]>
Venkad000
pushed a commit
to Venkad000/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment) Signed-off-by: Venkad Krishna C <[email protected]>
Venkad000
pushed a commit
to Venkad000/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment) Signed-off-by: Venkad Krishna C <[email protected]>
Venkad000
pushed a commit
to Venkad000/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment) Signed-off-by: Venkad Krishna C <[email protected]>
iii-i
pushed a commit
to IBM/dotnet-s390x
that referenced
this issue
Feb 7, 2025
fails with ping to dotnetbuilds.azureedge.net see dotnet/core#9676 (comment) Signed-off-by: Venkad Krishna C <[email protected]>
jonathanpeppers
pushed a commit
to dotnet/android
that referenced
this issue
Feb 10, 2025
Context: dotnet/core#9676 `ci.dot.net` is the new domain, used by `dotnet-install` scripts, for example.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We will be disabling use of
dotnetcli.azureedge.net
anddotnetbuilds.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:
dotnetbuilds.azureedge.net
dotnetcli.azureedge.net
We may disable the domains much sooner.
Test files:
Users should switch to
builds.dotnet.microsoft.com
andci.dot.net
, respectively, at their earliest convenience. Please email us at [email protected] if this is causing business continuity challenges.Context: #9671
The text was updated successfully, but these errors were encountered: