Plan to disable azureedge.net domains #9676
Assignees
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 <venkad@Venkads-MacBook-Pro.local>
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 <venkad@Venkads-MacBook-Pro.local>
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 <venkad@Venkads-MacBook-Pro.local>
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 <venkad@Venkads-MacBook-Pro.local>
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 <venkad@Venkads-MacBook-Pro.local>
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.
|
New domains builds.dotnet.microsoft.com and ci.dot.net were successfully set up and deliver content. Hey are our main delivery domains now.
|
|
I have created follow up work item as reminder for retiring dotnetcli.azureedge.net domain. |
|
@pavel-purma is that a private repo, or a broken link? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We will be disabling use of
dotnetcli.azureedge.netanddotnetbuilds.azureedge.netin 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.netdotnetcli.azureedge.netWe may disable the domains much sooner.
Test files:
Users should switch to
builds.dotnet.microsoft.comandci.dot.net, respectively, at their earliest convenience. Please email us at dotnet@microsoft.com if this is causing business continuity challenges.Context: #9671
The text was updated successfully, but these errors were encountered: