The wiki update is here:
https://github.com/makubacki/tianocore.github.io/blob/add_ci_uncrustify_instructions/EDK-II-Code-Formatting.md#how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci I am waiting for permissions to be updated so I can update the actual wiki page and then I'll send a patch for the plugin change with the link to that section.
Regards,
Michael
On 4/19/2022 6:15 PM, Michael Kubacki wrote:

I agree that is ideal but I'm not aware of how to do that at the moment.

Thanks,
Michael

On 4/19/2022 4:52 PM, Michael D Kinney wrote:

Hi Michael,

Can the build log provide a direct link to the log file artifact if an error is detected?

Mike

-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Michael Kubacki
Sent: Tuesday, April 19, 2022 12:42 PM
To: devel@edk2.groups.io; quic_rcran@...; spbrogan@...; Chao Li <lichao@...>
Subject: Re: [edk2-devel] Some questions about Azure CI

Hi Rebecca,

We are trying to keep the results reporting experience consistent with
other plugins and prevent an overwhelming amount of information being
printed to the build log.

In case other errors are present, providing high-level information from
each plugin can help point the user in the right direction to get more
detail.

I completely understand the concern though, so I'm planning to make
another step toward providing more information about how to debug an
issue, when it occurs. That is to put the step-by-step information about
where to find the file diff into the EDK II Code Formatting wiki page
and then if a failure occurs, print a link to that section of the wiki
page. I am hoping this will provide sufficient information to get to the
file diff at the point of failure.

I should be able to send these patches later today.

Regards,
Michael

On 4/19/2022 12:43 PM, Rebecca Cran wrote:

Since people are going to keep running into this, could we just output
the file diff to the console? That would avoid having to go hunting for
the log file.