Provide mechasnism to opt-out of DotNetCoreCLIV2 deprecation warnings
See original GitHub issueRequired Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: DotNetCoreCLIV2
Environment
-
Server - Azure Pipelines
-
Agent - Hosted
Issue Description
Every time the DotNetCoreCLIV2
task is used it now outputs this warning:
##[warning].NET Core SDK/runtime 2.2 and 3.0 are now End of Line(EOL) and have been removed from all agents. If you're using these SDK/runtimes, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the requied version.
This warning is displayed even if you aren’t using 2.2 or 3.0, and there doesn’t seem to be any way to opt out of this message. We are using:
- task: UseDotNet@2
inputs:
version: 3.1.300
This task needs to either:
- Ideally, detect the version of .NET Core in use and not display this warning
- Allow us to set an environment variable (or something) to not display the warning
This message spams our logs and hides warnings that may be actual problems:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:13 (10 by maintainers)
Top Results From Across the Web
DotNetCoreCLI@2 - .NET Core v2 task - Microsoft Learn
Build, test, package, or publish a dotnet application, or run a custom dotnet command.
Read more >Suppress warnings using .NET Core CLI task (DotNetCoreCLI ...
Trying to suppress warnings in Azure DevOps pipeline using .NET Core CLI task (DotNetCoreCLI@2), but getting the following error:.
Read more >Error when I try publish my web app DotNetCoreCLI@2
Hello everybody, I'm try to publish my web app with pipelines in DevOps. In my YAML file I used this cmd: - task:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The message should only be shown on hosted agents? That’s not the case, I also get it on a self-hosted agent.
I see that this has already been fixed by @tejasd1990