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
As demonstrated in https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#task-commands, for the ADO build summary page to list "warnings" and "errors" these have to be printed to stdout in a specific way. The Maven task does not do this, and I wager none of the other tasks either, so build warnings and errors can only be found in the complete build log. Maven's log format can be configured a small amount but not nearly enough to meet the ADO specification so the only means are with post-processing, like how the ADO Maven task does it.
Azure DevOps extension name and version
jfrog-azure-devops-extension *
JFrog CLI version
2
Operating system type and version
The text was updated successfully, but these errors were encountered:
Describe the bug
As demonstrated in https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#task-commands, for the ADO build summary page to list "warnings" and "errors" these have to be printed to stdout in a specific way. The Maven task does not do this, and I wager none of the other tasks either, so build warnings and errors can only be found in the complete build log. Maven's log format can be configured a small amount but not nearly enough to meet the ADO specification so the only means are with post-processing, like how the ADO Maven task does it.
Azure DevOps extension name and version
jfrog-azure-devops-extension *
JFrog CLI version
2
Operating system type and version
The text was updated successfully, but these errors were encountered: