在 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 daemon 构建它，没有它，但问题仍然存在.

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.

推荐答案

EDIT 看起来新版本的 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

[我们] 建议对开发人员的机器和持续集成服务器使用 [守护程序].

[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.

以前的回答

建议关闭daemon任何 CI 服务器.使用此选项禁用它

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

--no-daemon

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