Build steps that execute in sequence, e.g. https://dev.azure.com/dnceng-public/public/_build/results?buildId=1427514&view=logs&s=ff05ad62-bb9a-53b6-ce9f-72f329a63e7c&j=2709a726-7db6-5829-ca7b-958b9d664f9e specify different build logs but the second build step will just overwrite the original build log. This is apparently because multiple /bl: specifications just result in the same binlog written multiple times, not an override of the first switch.
Update the eng/common scripts to allow specification of the binlog name.
Build steps that execute in sequence, e.g. https://dev.azure.com/dnceng-public/public/_build/results?buildId=1427514&view=logs&s=ff05ad62-bb9a-53b6-ce9f-72f329a63e7c&j=2709a726-7db6-5829-ca7b-958b9d664f9e specify different build logs but the second build step will just overwrite the original build log. This is apparently because multiple /bl: specifications just result in the same binlog written multiple times, not an override of the first switch.
Update the eng/common scripts to allow specification of the binlog name.