I have some programs (which I do not have source access to) that update a progress bar on one line of the console, which looks fine when run from a command prompt. But when TeamCity runs these programs and captures stdout, it captures each update as a separate line, which is taking up a huuuuuuuge amount of space in logs. Is there some way to improve this behaviour? I'm running TeamCity 2018.1 (build 58245).
This is the kind of thing I'm talking about (imagine this reported tens of thousands of times):
[09:15:55][Step 2/2] MyScript: Waiting... (|)
[09:15:55][Step 2/2] MyScript: Waiting... (/)
[09:15:56][Step 2/2] MyScript: Waiting... (-)
[09:15:56][Step 2/2] MyScript: Waiting... (\)
[09:15:56][Step 2/2] MyScript: Waiting... (|)
[09:15:56][Step 2/2] MyScript: Waiting... (/)
[09:15:56][Step 2/2] MyScript: Waiting... (-)
[09:15:56][Step 2/2] MyScript: Waiting... (\)
[09:15:56][Step 2/2] MyScript: Waiting... (|)
[09:15:56][Step 2/2] MyScript: Waiting... (/)
[09:15:56][Step 2/2] MyScript: Waiting... (-)
[09:15:57][Step 2/2] MyScript: Waiting... (\)
[09:15:57][Step 2/2] MyScript: Waiting... (|)
[09:15:57][Step 2/2] MyScript: Waiting... (/)
[09:15:57][Step 2/2] MyScript: Waiting... (-)
[09:15:57][Step 2/2] MyScript: Waiting... (\)
[09:15:57][Step 2/2] MyScript: Waiting... (|)