[GRADLE-1196] Support for putting debug build log output to file Created: 29/Oct/10  Updated: 12/Dec/16  Resolved: 12/Dec/16

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Gretar Rafn Arnason Assignee: Unassigned
Resolution: Duplicate Votes: 15


It would be nice to be able to put debug level build log output into a file while retaining info level build log output in the console.
That way it is possible to peek into the log file when the console output indicates a problem.

Comment by Iain [ 07/Aug/13 ]

I see this feature has a long history and is on the roadmap for "someday". I would like to add my desire to see this feature in a release hopefully not too far away.

For information, our use case; when running long database updates, in the event of a failure its often helpful to have a log file to digest and debug (sometimes non developers run these tasks). As some database deployments can overrun the size of the buffer, a text file would be desirable.

Comment by Gerd Boerrigter [ 11/Jun/14 ]

We are in the process of transforming the ant and groovy file for running our integration test to gradle.

In ant we use the record target to write multiple logfiles with different log levels. One file with little information is automatically examined to point out the failed test case. A verbose file might be used by a developer to correct programming errors.

We really like to give a destination for the log files. A plus would be to have different files depending on the log level or other things, like the used logger. A configurable log4j.properties could also get the job done.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Stalle [ 16/Nov/16 ]

I feel this would be a valuable addition. Let's says that there is some flaky build code or tests, having a more complete build/test log on disk would simplify debugging when reproducing is not always easy.

Comment by Stalle [ 12/Dec/16 ]

I created https://github.com/gradle/gradle/issues/1005 for this.

Comment by Benjamin Muschko [ 12/Dec/16 ]

Thanks for creating the issue on GitHub, @Stalle.

Generated at Wed Jun 30 11:49:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.