From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I wonder how many of you put `-q` for your CI jobs already? I see huge but it looks like I'm not interested in. I have other tools to monitor times and cacheability. If something fails - it is still printed in log.

I always use `-i` and `-s` in CI and would never use `-q`

Because if there is a failure, I want as much information as sensibly possible

The pure error very often contains not enough information

Even on local builds I most often use either no option or `-i` if I need more information.
`-q` I most often only use if I want to parse the output of a task for some reason.

I just saw <https://github.com/nomisRev/agent-tools-for-kotlin|github.com/nomisRev/agent-tools-for-kotlin> and was thinking that maybe a good direction

Sure there is also tools like `snip` but that still write a full log on disk

&gt; nudges the LLM/Agent to always specify `-q` flag to avoid Gradle's verbose output
This sentence in itself seems quite wrong.
Gradle used to output much more on lifecycle level and moved many things to info level to not spam the console by default.
If there is too much output in a build, that is most probably because non-built-in-plugins or build logic either uses lifecycle level too lightly, or use `stdout` which also lands on lifecycle level by default.
If that is the case, those should probably adapted to move more logging to info level. :man-shrugging:

Not sure if it is true for android module gradle build and having build variant makes things even worse

If you want a short log, but still have the log I advise `build-brief`

It's surprisingly good in standard tasks, but not so much in other gradle tasks, so YMMV.

Is it alternative for snip? <https://edouard-claude.github.io/snip/|edouard-claude.github.io/snip>

&gt; Not sure if it is true for android module gradle build and having build variant makes things even worse
Quite possible, but then exactly what I said.
AGP or whatever overusing lifecycle logs or `stdout` and should be improved.
:man-shrugging:

What is `build- brief`?

THis tool <https://gradle-community.slack.com/archives/CAHSN3LDN/p1778528286153439|https://gradle-community.slack.com/archives/CAHSN3LDN/p1778528286153439>, also sorry there was typo, it's `build-brief`.