[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: excessive java precommit logging

I'm not sure what we lose by dropping the --info flag, but I generally worry about reducing log output since logs are the main resource for diagnosing Jenkins build errors.

It seems the issue is that Chrome doesn't scale well to large log files. A few alternative solutions:

1. Use the produced Build Scan (example: [1]) instead of the raw console log. The build scan is quite useful at pointing to what actually failed, and filtering log output for only that task.
2. Instead of consoleFull, use consoleText ("View as plain text" link in Jenkins), which seems to be much easier on Chrome
3. Download the consoleText output locally and use your favorite log viewer that can scale to large files.

On Wed, Dec 19, 2018 at 10:42 AM Udi Meiri <ehudm@xxxxxxxxxx> wrote:
Hi all,
I'd like to reduce precommit log sizes on Jenkins. For example:
is 79M, which makes Chrome sluggish to use on it (tab is constantly using a whole cpu core).

I know this might be controversial, but I'd like to propose to remove the --info flag from the gradlew command line.