Change DotNetCoreCLI verbosityRestore defaultValue to Normal

[aarondandy]

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Feature

Enter Task Name: DotNetCoreCLIV2

Environment

• Server - Azure Pipelines:

  • If using Azure Pipelines, provide the account name, team project name, build definition name/build number: N/A

• Agent - Hosted:

  • If using Hosted agent, provide agent queue name: Azure Pipelines

Issue Description

The default verbosity when creating a dotnet restore task is set to Detailed instead of Normal which causes a lot of output that I rarely need. It produces quite a lot of output which is not very helpful to me, making it a bit more difficult to read the logs if I just want to know "what" is going on vs "why". Additionally I don't have a way to reliably time this but it seems that it can add 10% to the runtime of the task. Can the default verbosity for this task be changed to Normal instead of Detailed to provide some of us with a better user experience and to possibly reduce our build times some? I would like to change it to Detailed when needed.

The fix for this appears to be as simple as changing the default value in the task.json file. I would be happy to make a PR for it but I am unable to properly contribute until #11136 is resolved.

azure-pipelines-tasks/Tasks/DotNetCoreCLIV2/task.json

Line 265 in 150d937

"defaultValue": "Detailed",

[aarondandy]

I made a PR for it anyway. The bots will sort it out in the end 😉

[aarondandy]

After looking at the docs, it seems that Minimal is the default used by the tool and may make a better default for the tool.

Docs: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-restore#options

[bishal-pdMSFT]

For CI pipeline normal may be better middle path as it might offer more insights and save people from re-running failed release with updated verbosity. From: Aaron Dandy <notifications@github.com> Sent: Wednesday, February 5, 2020 10:23 PM To: microsoft/azure-pipelines-tasks <azure-pipelines-tasks@noreply.github.com> Cc: Bishal Prasad <biprasad@microsoft.com>; Assign <assign@noreply.github.com> Subject: Re: [microsoft/azure-pipelines-tasks] Change DotNetCoreCLI verbosityRestore defaultValue to Normal (#12297) After looking at the docs, it seems that Minimal is the default used by the tool and may make a better default for the tool. Docs: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-restore#options<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fcore%2Ftools%2Fdotnet-restore%23options&data=02%7C01%7Cbiprasad%40microsoft.com%7C61113fa4d14148eb81ae08d7aa5bd4a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637165183694110048&sdata=iWeANn87Y0BrTZGErLicw9l8N1d0rYoPK%2Bi%2FPnBH2b0%3D&reserved=0> — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fazure-pipelines-tasks%2Fissues%2F12297%3Femail_source%3Dnotifications%26email_token%3DAB3XU7NVRQJ2DS4DQXYTFXDRBLVF7A5CNFSM4KQCRPQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK4EXCY%23issuecomment-582503307&data=02%7C01%7Cbiprasad%40microsoft.com%7C61113fa4d14148eb81ae08d7aa5bd4a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637165183694120003&sdata=iBQPBD4Khci7WdljZaVRSrCV5b8OAYiTweH8YSk9l8s%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB3XU7IPIOMDI7PEVTM33U3RBLVF7ANCNFSM4KQCRPQA&data=02%7C01%7Cbiprasad%40microsoft.com%7C61113fa4d14148eb81ae08d7aa5bd4a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637165183694120003&sdata=EHERDb7Kwa712aVMMiRPhterYaE2buZhvQyfESkigYk%3D&reserved=0>.

[aarondandy]

OK, that is a fair compromise. Normal isn't all that more noisy than Minimal. I also doubt anybody will be broken by the difference either way, and if they are they can manually configure it.

[github-actions]

This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days