Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow Gradle daemon to continue running between build steps
See original GitHub issueThe current implementation uses the --no-daemon flag to avoid the need to stop daemons at the end of the job. Instead, we should run the build as configured, keeping track of invocations and running gradle --stop as required at the end of the job.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:5 (2 by maintainers)
Top Results From Across the Web
The Gradle Daemon
To disable the Daemon for all builds of a project, add org.gradle.daemon=false to the gradle.properties file in the project root. Disable for a...
Read more >"Starting Gradle daemon" loop creating endless processes
As a result, the build never finishes and it keeps creating Gradle daemon processes until the system runs out of memory and freezes....
Read more >The Gradle Daemon - API Manual
The Gradle Daemon is enabled by default starting with Gradle 3.0, so you don't have to do anything to benefit from it. If...
Read more >Command-line options | Gradle Effective Implementation Guide
--no-daemon Do not use the Gradle daemon to run the build. ... Let's run the Gradle command from the parent directory of our...
Read more >How to decrease your Gradle build time by 65%? - Medium
Enable daemon: ... Gradle has a very good feature called Gradle Daemon. Daemon keeps the instance of the gradle up and running in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As of v2.1, the daemon is still disabled, but is done via
org.gradle.daemon=falsein~/.gradle/gradle.properties.This means that, pending a fix to this issue, a workflow can provide the
--daemoncommand-line argument when invoking Gradle. Any job that does so will be responsible for stopping the Gradle daemon in a later Step.Thanks for the fix! Nice to have it now right by default 🙂