UseDotNet@2 cant find sdk version matching 3.x
See original GitHub issueNote
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name:UseDotNet@2
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment
-
Server - Azure Pipelines
-
Agent - Private Windows 10
Issue Description
Unable to find a matching version of DotNetCore sdk for 3.x Including parameter includePreviewVersions finds the latest preview version of 3.1, but I want the latest current version. (currently 3.0.100)
##[section]Starting: UseDotNet
==============================================================================
Task : Use dotnet
Description : Acquires a specific version of the .NET Core SDK from the internet or the local cache and adds it to the PATH. Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support.
Version : 2.0.5
Author : Microsoft Corporation
Help : https://aka.ms/AA4xgy0
==============================================================================
Tool to install: .NET Core sdk version 3.x.
##[error]Failed while getting version 3.x from channel 3.1 with error: {}
##[error]sdk version matching: 3.x could not be found
##[section]Finishing: UseDotNet
Error logs
##[error]Failed while getting version 3.x from channel 3.1 with error: {}
##[error]sdk version matching: 3.x could not be found
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:15 (5 by maintainers)
Top GitHub Comments
While changing it to 3.0.x works, 3.x should still work as well. This broke my pipelines as well, and the documentation still states that using Major.x will supply the latest Minor version.
I have just changed mine to 3.0.x - I guess work has started on the 3.1 branch so, for stability, it is probably best to use 3.0.x.