Consider adding a message indicating binlog creation.

[AR-May]

Currently, when using the /bl flag, there is no clear message in the build logs indicating that a binlog file is being created or specifying its location. This can cause confusion for customers who could expect confirmation or details about the binlog file in the textual logs.

[baronfel]

In the extreme, it could be good to have a record of all loggers that would generate files: binlog, file logger, etc. I'm not sure I'd want this message to show on default verbosities though - unless we can group/show them nicely along the lines of #12114.

[AR-May]

I agree, the information of all loggers that were used, and their generated files, should be at least in the diagnostic console log and in binlog. If we cannot integrate this information with Terminal Logger, it is fine so far as it is there.

For binlog specifically, I think about the following use case for such a message: debugging CI runs, for the reason why binlog is not published to the artifacts. In this case it would be enough to show it with normal or detailed verbosity in the console logger.

[baronfel]

The arcade targets actually write a message to stdout if the build failed with an error pointing to the binlog.

Having something clickable would be a lovely improvement.

[AR-May]

Oh, that is probably why I thought that this message should already exist, before I actually checked and did not find it.

[baronfel]

@AR-May I think I have the right location:

both the console logger and the terminal logger have a concept of a 'build summary' - a trailing report of the build. It seems very natural to add these log entries there, that way they do not get lost at the 'start' or middle of the build output