Providing build output in Azure

[nick5454]

I would like to show build results when failed. Has anyone found a good way to show this in Azure so the developers know it's build error?

Is there a helper extension out there that helps on this?

[devlead]

@nick5454 can you clarify what you mean about outputting to Azure? Are you talking about Azure DevOps or something like Azure Monitor / AppInsights?

[nick5454]

This is in Azure Devops. The developers check in code that has errors and I'm looking for a way to show the errors reported when calling MSBuild inside my cake script.

I'd like to add a build error tab inside the pipeline results, so they can see the errors. But. i'm hoping there is a cake package set up for this already.

[devlead]

Ah then the Cake.BuildSystems.Module is probably what you're looking for.

You can add that to your script using the module pre processor directive

#module nuget:?package=Cake.BuildSystems.Module&version=0.3.2

Depending on your version of Cake you might need to bootstrap script first using --boostrap switch.

I.e.

dotnet cake --bootsrap build.cake
dotnet cake build.cake

[pascalberger]

Cake.Issues addins might be of interest to you. The MsBuild provider allows to parse an MsBuild logfile for errors and warnings which you then can pass to a report provider to Create an HTML report or a SARIF file which you then can show as a build tab using the Azure DevOps SARIF SAST Scans Tab extension.

See here for an example of the second approach.

Cake.Issues addins would allow you to also further process the errors and warnings, e.g. by writing them as comments to pull requests.

[nick5454]

Awesome! Thanks for the advice

[nick5454]

@pascalberger That is a great tool and really great UI debugging.

Is there a way to customize the tab name from "Scans" to something else like "Build Info"?

[pascalberger]

@nick5454 I'm not aware of any. But you might want to post the question in the Q&A section of the extension.

For this extension I unfortunately also don't know if source code is available and where. The predecessor extension had its source code available and there the name of the tab was hardcoded. But the new extension doesn't seem to be releases from this repo anymore as last commit doesn't match last publish date of the extension.

[nick5454]

@pascalberger Thanks so much for the tips