I recommend not to run the daemon in CI. It's not worth the
instability to gain a few seconds on each run.

On Mon, Dec 24, 2018 at 7:45 PM Jacques Le Roux
<jacques.le.r...@les7arts.com> wrote:
>
> Hi,
>
> So far, from Gradle team recommendation, we were not using Gradle daemons in 
> demos and Buildbot builds.
>
> In both, I recently noticed warnings like
>
>     To honour the JVM settings for this build a new JVM will be forked. 
> Please consider using the daemon:
>     https://docs.gradle.org/5.0/userguide/gradle_daemon.html. Daemon will be 
> stopped at the end of the build stopping after processing
>
> There I can read:
>
>     /Continuous integration//
>     //Since Gradle 3.0, we enable Daemon by default and recommend using it 
> for both developers' machines and Continuous Integration servers. However,
>     if you suspect that Daemon makes your CI builds unstable, you can disable 
> it to use a fresh runtime for each build since the runtime is
>     //completely//isolated from any previous builds./
>
> I think we can try it, what do you think?
>
> Also, I'm using --/parallel /for quite a moment now. Since we switched to 
> Gradle 5 I no longer see warnings about that. Should we not use it in demos
> and Buildbot builds and maybe enforce it generally?
>
> Thank you for your opinions.
> //
>
> Jacques
>

Reply via email to