在Jenkins上构建Android项目时，Gradle构建守护进程意外消失(可能已被杀死或崩溃) [英] Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) while building Android project on Jenkins

问题描述

我有一个可以在Android Studio上成功构建的Android项目.

I have an Android Project that builds successfully on Android Studio.

现在，我想在Jenkins上构建它.但是，当我这样做时，出现以下错误: Gradle构建守护进程意外消失(可能已被杀死或崩溃)

Now I want to build it on Jenkins. But when I'm doing I got the following error: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

例外是:

org.gradle.launcher.daemon.client.DaemonDisappearedException: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
    at org.gradle.launcher.daemon.client.DaemonClient.handleDaemonDisappearance(DaemonClient.java:222)
    at org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:198)
    at org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:162)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:125)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:80)
    at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
    at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
    at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:241)
    at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:214)
    at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
    at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
    at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:207)
    at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
    at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
    at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
    at org.gradle.launcher.Main.doAction(Main.java:33)
    at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
    at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
    at org.gradle.launcher.GradleMain.main(GradleMain.java:23)

我阅读了相关主题，但无济于事.我尝试使用gradle守护程序来构建它，并且没有它，但是问题仍然存在.

I read related topics, but it does not help. I tried to build it using gradle daemon, and without it, but the problem still exists.

推荐答案

编辑>似乎新版本的Gradle进行了一些更改.

EDIT Looks like there has been a few changes with the new versions of Gradle.

从3.0版本开始，您应该不要禁用CI上的守护程序了

Since 3.0 you should not disable the daemon on your CI anymore

[我们]建议将[守护程序]用于开发人员的计算机和Continuous Integration服务器.

[We] recommend using [the daemon] for both developers' machines and Continuous Integration servers.

但是，如果您怀疑Daemon使CI构建不稳定，则可以将其禁用以对每个构建使用全新的运行时，因为该运行时与任何先前的构建完全隔离.

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.

上级答案

建议在任何CI服务器上关闭daemon .使用此选项将其禁用

It's recommended to turn off daemon on any CI server. use this option to disable it

--no-daemon

这篇关于在Jenkins上构建Android项目时，Gradle构建守护进程意外消失(可能已被杀死或崩溃)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！