-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[BUG]: ##[error]Failed to download or parse releases-index.json with error: {} #20159
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
Comments
Azure Artifacts does not own any part of the UseDotNet task |
@jmyersmsft how is Azure Artifacts related? I saw that the source code for the UseDotNet task is in the current repo where I've opened this tickeet. |
Sorry, this is indeed the correct repo, just the "Area: Artifacts" label was not. |
Thanks for the reporting! We are working on higher priority issues now, but we'll get back to this one soon |
We have the same issue. any update? |
The error message is as follows, we are really in pain, hope it will be resolved soon |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
New issue checklist
Task name
UseDotNet@2
Task version
2.238.1
Issue Description
This happens more and more frequently and people are complaining in an existing issue #10969 for the past months. It seems like a capacity issue at the endpoint where releases-index.json is downloaded from. Even if it succeeds sometimes it takes minutes to complete.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu
Relevant log output
Tool to install: .NET Core sdk version 6.x. ##[error]Failed to download or parse releases-index.json with error: {} Finishing: dotnet use 6.x
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: