Our goal is to understand where the time goes in our builds. More importantly, we want other developers to be able see it easily and witness the improvement or degradation of the build performance. The binary log is great, but we cannot have each Pull Request validation build produce one because it prolongs the duration of the build itself significantly. Plus one cannot really draw charts and present dashboards from a collection of binary logs.
We have decided to write our own logger in order to measure the events and push them to Application Insights. I hope to be able to publish the source code on GitHub really soon.
Events
Our logger subscribes to the following msbuild events:
Simetimes a WinDBG command produces a lot of output that we may not wish to see in the GUI. Sometimes we would like to run a complex post-processing on
a WinDBG command output. These are two examples of cases when scripting WinDBG and redirecting the output into a file is what we want to do and this
script is a way to do it.
WinDBG and CDB are two front-ends for the same debugger. The difference is the user interface - WinDBG is a GUI whereas CDB is console based.
You can’t perform that action at this time.
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.