Listing things that could be captured from binlog files

[StanleyGoldman]

• With clean build logs...
  • With a single build log...
    • Figure out how to use Roslyn Code Fixes to suggest fixes
  • With a history of build logs...
    • Raise warnings for spikes in increase in build time
    • Listing updated nuget packages and other assemblies

[KirillOsenkov]

One idea is listing MSBuild double-writes:
https://github.com/KirillOsenkov/MSBuildStructuredLog/blob/master/src/StructuredLogger/Analyzers/DoubleWritesAnalyzer.cs

This is when files from two or more different sources are copied to the same destination file path, overwriting a previously copied file. These are often non-deterministic and a source of random build or runtime failures. See https://github.com/KirillOsenkov/MSBuildStructuredLog/wiki/Double-write-detection.

[pascalberger]

How do you plan to implement history of build logs? By storing logs in the application or do they need to be provided by the user (e.g. by retrieving them from artifact of previous build run)?

[StanleyGoldman]

Just throwing ideas around... We have a document based database in our web service, if we figured out something we wanted to track between builds we could store it there.