1、问题现象

1.1、Slave went offline during the build

1.2、useNewCruncher has been deprecated. It will be removed in a future version of the gradle plugin. New cruncher is now always enabled.

Incremental java compilation is an incubating feature.

2、问题分析&定位

从上诉两个log日志信息来看，有两种可能：

1、gradle 在构建过程中，Jenkins slave agent 的daemon异常，导致slave offline，从而build failed

2、引入了其他的Java编译方式，及一些被deprecated的api

那么我就依据初步分析的这两个可能问题去Google

3、问题解决

3.1、依据Google中各路大神对第二个问题的解析，并根据解决方案进行尝试，均无功而返。

3.2、参考Stack Overflow中对：“Why did the Gradle Daemon die?”的文章中，大神是这样解答的：

Gradle build daemon disappeared unexpectedly most frequently occurs when something else kills the long-running Gradle Daemon process and the client process (the Daemon uses local TCP connections to communicate) tries to send a message and gets no response.

For example, running gradle --stop or killall java while a build is occurring will reproduce this problem.

附文章链接：https://stackoverflow.com/questions/29660238/why-did-the-gradle-daemon-die