Build you sent is still building :). What about previous one, command which failed is cmake --build . --config %CONFIGURATION% --target package. I do not believe that we can create good summary for every custom command... To understand what command is failed you can just scroll up from the end till latest command called by build scenario (line in cyan color) and investigate traces after that.
Actually I agree that scrolling up and looking for line in cyan is not very convenient, we need to improve that.
The system must know that this is an error, because it knows to highlight it in red. Couldn't it put a copy of this information at the top (in the summary) or at the end of the build log?
There were also warnings, which it would be great to be able to see on the "messages" tab as well:
No artifacts found matching 'packages\BoxBackup-*.zip' path
No artifacts found matching 'packages\BoxBackup-*.exe' path
Also, is there anything you can do to speed up logfile loading? It seems much slower than Travis for example, and it also doesn't appear to use the browser cache, since it takes ages to load every time I visit the page.
Filed this issue to track slow console loading with long logs.
Not sure about error summary though. Error message is not always complete enough to make good conclusions and root cause of error can be actually found somewhere much earlier in logs.