Can binlogs have customized names?

In a discussion on this PR, it came up that Arcade prefers repos to always use the default build.binlog name as a piece of shared infra. There was also discussion of a loss of ability to do analysis on repo’s binlogs when we customize their names. Currently AspNetCore gives its binlogs distinct names, the reasoning being that it’s easier to identify a downloaded binlog that way, and that several of our CI legs are broken into multiple steps, each of which produces a binlog (e.g. the Windows build does x64, x86, then installers, sequentially). I wanted to open a discussion to see if we could reach a conclusion on what’s right here.

CC @markwilkie @tmat @dougbu

[markwilkie]

@wtgodbe - I presume you’re also ok w/ closing this issue given both the discussion and the approach @dougbu is going with?

[dougbu]

Just noticed even Arcade’s pipeline has multiple build steps in some of its jobs. But, its approach makes it clear we don’t need anything more. -ci … /bl:{some path} works fine. (I was wondering this about the previous “workaround” in dotnet/aspnetcore.)