You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating our first apps to .NET 8 I once again stumbled over the ancient messages writen by DotNetCoreCLI@2 about .NET 2.2, 3.0 and 5.x.
We are using Azure DevOps Server in latest version and use only support .NET runtimes/SDKs. Our Devs ask every than and now why these messages still pop up.
I would like to see this message removed or at least give us an environment variable (e.g. SKIP_HOSTED_AGENT_INFOS) to skip these messages
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2022.0.1
Operation system
Windows Server 2022
Relevant log output
Starting: Install dotnet tools
==============================================================================
Task : .NET Core
Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command
Version : 2.202.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
==============================================================================
C:\Windows\system32\chcp.com 65001
Active code page: 65001
Info: .NET Core SDK/runtime 2.2 and 3.0 are now End of Life(EOL) and have been removed from all hosted agents. If you're using these SDK/runtimes on hosted agents, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the required version."C:\Program Files\dotnet\dotnet.exe" tool restoreTool 'dotnet-ef' (version '8.0.0') was restored. Available commands: dotnet-efRestore was successful.Info: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://docs.microsoft.com/en-us/dotnet/core/tools/ and https://docs.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshootingFinishing: Install dotnet tools
Full task logs with system.debug enabled
[REPLACE THIS WITH YOUR INFORMATION]
Repro steps
No response
The text was updated successfully, but these errors were encountered:
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
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
DotnetCoreCLIV2
Task version
No response
Issue Description
After updating our first apps to .NET 8 I once again stumbled over the ancient messages writen by DotNetCoreCLI@2 about .NET 2.2, 3.0 and 5.x.
We are using Azure DevOps Server in latest version and use only support .NET runtimes/SDKs. Our Devs ask every than and now why these messages still pop up.
I would like to see this message removed or at least give us an environment variable (e.g. SKIP_HOSTED_AGENT_INFOS) to skip these messages
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2022.0.1
Operation system
Windows Server 2022
Relevant log output
Full task logs with system.debug enabled
Repro steps
No response
The text was updated successfully, but these errors were encountered: