@bot-gradle test QFL

OK, I've already triggered the following builds for you:

• QuickFeedbackLinux build

I don't think we should do this, but I agree that the current output could be more useful. I'd rather make the output more useful in some small way over turning it off entirely.

This pull request has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be closed if no further activity occurs. If you intend to work on this pull request, please ask the team to reopen the PR or push a new PR. Thank you for your contributions.

For what it's worth Gradle's own help output contains this:

-q, --quiet                        Log errors only.

I don't see how this annoying and repetetive help message qualifies as an "error". I would rather prefer that -q suppressed it, just like the help actually promises. If I execute ./gradlew -q run and the application dies with an exception, I don't want to see ten lines of useless crap that does nothing but distract me of actual application output. It's not like -q is the default, so if I put it there then it is an active user decision, but apparently it only suppresses build progress output.

Tested with Gradle 8.4.

One thing to note here is that there's an inconsistency in the build output when --quiet is present. For successful builds, the BUILD SUCCESSFUL message is not printed. For failing builds, the BUILD FAILED message is present.

I'm leaning towards implementing the proposed behavior.

At the same time, we currently don't have the capacity to work on this. Would anyone be interested in creating a pull request?

Related: #28373.

I think we should try to get something done IRT this. There seems to be a good amount of sustained interest.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If you don't want the stale bot to close it, then set a milestone for it.

@donat - You closed the linked issue as Not Planned. Should this be closed, too?