Open tdashworth opened 3 years ago
Wondering if it would be worth refactoring the logging stuff to follow something similar to Nuke with different "OutputSinks" for different CI providers?
https://github.com/nuke-build/nuke/tree/2e3ebee5b041bb80d18d41a9da36b7e7d8fd28fc/source/Nuke.Common/OutputSinks https://github.com/nuke-build/nuke/tree/2e3ebee5b041bb80d18d41a9da36b7e7d8fd28fc/source/Nuke.Common/CI/AzurePipelines
I'm not sure if these work in Releases which is where our deployment run.
Is your feature request related to a problem? Please describe
When viewing the logs for a deployment on Azure DevOps, it is quite frustrating to scroll through the whole log to find a specific section.
Describe the solution you'd like
I would like to use Azure Pipeline's logging commands to group sections that can be minified. I'm not sure at what level would be best to group, the lifecycle or the deployment steps?
https://docs.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#formatting-commands