-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: UseDotNet@2
does not download .NET 8 SDK
#19292
Comments
UseDotNet@2
does not download .NET 8 SDK from global.json
UseDotNet@2
does not download .NET 8 SDK
Use 8.0.1 or 8.0.100 for the SDK version. |
Thanks, 8.0.1 didn't work, but 8.0.100 did within |
@StormPooper as for now the task only looks at the The bug is there, in the method |
Thanks @paule96, I'll let you know if I get a chance to look at it. |
### What - Update Depedabot File - Expand tracking of external nugets - Add additional reviewer - Prune tracking where no reference exists - Update global.json to an explicit DotnetSDK version ### Why - Review of dependabot file found it was out of date - Due to microsoft/azure-pipelines-tasks#19292 ADO must see explicit SDK version references as the rollForward field is not respected, instead requiring custom wildcarding incompatible with global.json ### Tested Nope
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 |
Still an issue. |
Can confirm, would be great if, at the very least, the task would look at the rollforward setting as well. |
Would be great to have this fixed in the latest task version to properly support rollForward policy. |
Causing me issues as well. I expected that this task would behave the same as the .NET CLI |
Still an issue. :-( |
That is so annoying. Why can't this be fixed? |
It would be ideal to have this resolved in the latest task version to ensure full compatibility with the rollForward policy. |
This is preventing build pipelines from fetching the specified version and needs to get fixed. Why can't the build tools work as expected? |
@FreeApophis this is not how it works. If it annoys you, fix it. I did write a year ago what are the interesting files to fix it. Currently I don't use it by myself. (or not in that way) |
@paule96 I think @FreeApophis was of the impression - like me - that this is an officially supported repository by microsoft. It is just puzzling to me that such core-tasks are not directly coming from Microsoft to be honest 😶 |
For me this step fails with version 8.0 but passes with version 8.x |
Also fails for |
New issue checklist
Task name
UseDotNet@2
Task version
2.230.2
Issue Description
I'm attempting to use
UseDotNet@2
withubuntu-latest
to install .NET 8 now it has been released, but I get the following error:I've checked releases.json and it has a non-preview build for linux, so it should be finding it, but it fails. I've tried this with the
global.json
below and by specifyingversion: 8.0.0
instead, both with and without theincludePreviewVersions
flag.Task in
azure-pipelines.yml
:global.json
: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-latest
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: