[GRADLE-3265] New Gradle Daemon process holding up the buildbot CI step on Windows Created: 20/Mar/15 Updated: 23/May/16 Resolved: 23/May/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | ||
| Reporter: | Gradle Forums | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
I am runninng the gradle via our CI server implemented in buildbot, the daemon starts up however it is being considered a child of the process that started it which in turn leaves the job run hanging until it timeouts. Once I kill the java daemon process the the job successfully finishes. This happens on windows machine (windows 7 service pack 1) any idea what might be causing this or how I might avoid it? Let me know if additional information is needed. |
| Comments |
| Comment by Gradle Forums [ 20/Mar/15 ] |
|
Right now, the recommendation is to not use the daemon for CI builds because it mixes state from previous builds with the current one and causes problems with some CI servers (like you've seen). We're updating the Daemon chapter to reflect that. |
| Comment by Michael Barnathan (Inactive) [ 19/May/16 ] |
|
How is the CI task checking for the continued existence of the daemon? |
| Comment by Michael Barnathan (Inactive) [ 23/May/16 ] |
|
Assuming it's this, which seems to be checking for continued process existence. It doesn't seem to have any support for tracking backgrounded processes, so this seems inherently/conceptually incompatible with the daemon (which is designed to keep the process running). I'd recommend simply disabling the daemon with the flag in this application; I doubt it would ever work satisfactorily without making significant changes to buildbot. |