Search Issue Tracker
Fixed in 2018.1
Fixed in 2017.4, 2018.2
Votes
0
Found in
2017.3.1p2
Issue ID
1041385
Regression
No
Do Not Kill other gradle daemons when build completes
Do not kill other instances of gradle when a gradle build completes.
We build mutiple android projects on the same build machine. When we build two or more Android builds, the first Android build will send out a command to shutdown all other gradle builds running. We see the following from the closed builds:
Gradle build daemon has been stopped: stop command received
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Changing ip address of cache server v2 doesn't reconnect.
- Aplying changes to root prefab in a nested prefab undo changes made to the child prefab
- [2018.4][UWP] Exception is thrown 'Unable to find method PostprocessStacktrace in [UnityEngine.CoreModule.dll]'
- Sub Emitter particle's width is twice its height when Separate Axes in the Size over Lifetime module is enabled
- Animation does not play correctly when Optimized Game Object functionality is used and a Child GameObject is added to bone
Petr777
Sep 10, 2019 08:39
Looks like unchecking "Stop Gradle daemons on exit" in "Preferences/External Tools" fixes this issue
Petr777
Sep 10, 2019 08:23
Exists in 2018.4.4f1
zach_peoplefun
Aug 29, 2019 14:41
Issue still exists in 2019.1.5f1