Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

terminal logger not that usable in practise #11001

Open
rmannibucau opened this issue Nov 19, 2024 · 0 comments
Open

terminal logger not that usable in practise #11001

rmannibucau opened this issue Nov 19, 2024 · 0 comments

Comments

@rmannibucau
Copy link

Hi,

I really like the terminal logger feature but it has a big pitfall, it breaks all the outputs by default which means any failing build needs to run without it more or less.

What would be neat is to keep the terminal logger feature AND the output.
One way is to "split" the output in two parts, the build output (at the top for ex) and the "dynamic" output (tl) at the bottom - think gradle does it or was doing it at least.
An alternative is what maven daemon does (once well configured), ie assign N lines (N >= 1) per project, have the first line being the terminal logger and the other lines the build output of this project. Finally you stack the projects and you get an in between feedback.
Last option is to just dump the output on failure (capturing in a file during the build for ex).

Hope it makes sense

@rmannibucau rmannibucau changed the title terminal logger not that usable i npractise terminal logger not that usable in practise Nov 19, 2024
@marcpopMSFT marcpopMSFT transferred this issue from dotnet/sdk Nov 19, 2024
@JanKrivanek JanKrivanek reopened this Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants