离子cordova android构建失败，在大厅ci上说“ Gradle build守护进程退出”
[英]Ionic cordova android build fails on concourse ci by saying “Gradle build daemon got exited”
问题描述
We are currenly migrating an Ionic android build setup from bamboo to concourse. 
我们目前正在将Ionic Android构建设置从Bamboo迁移到Concourse。 The android build using ionic cordova is triggered as one of the commands in a larger concourse-ci job which does npm install first and then does ionic build command. 使用离子cordova的android构建会作为较大的concourse-ci作业中的命令之一触发，该作业先安装npm，然后再执行ionic build命令。
The actual ionic command that fails is : 失败的实际离子命令是：
ionic cordova build android --dev --debug --release --no-interactive --no- confirm --buildConfig --nofetch --minifyjs --minifycss --gradleArg=--no-daemon
As a prerequisite to ionic cordova, I have ensured that gradle is installed correctly in the base docker image by doing wget of the gradle distribution and setting the gradle home environment variable to point to the downloaded gradle binary. 作为离子cordova的先决条件，我通过执行gradle分发的wget并将gradle主页环境变量设置为指向下载的gradle二进制文件，确保gradle已正确安装在基本docker映像中。 Following is the content of the dockerfile : 以下是dockerfile的内容：
FROM runmymind/docker-android-sdk
# make /bin/sh symlink to bash instead of dash:
RUN echo "dash dash/sh boolean false" | debconf-set-selections \
&& DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dash
# Installing NodeJS
RUN ARCH=x64 \
&& curl -SLO "https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION-linux-$ARCH.tar.xz" \
&& curl -SLO --compressed "https://nodejs.org/dist/v$NODE_VERSION/SHASUMS256.txt.asc" \
&& tar -xJf "node-v$NODE_VERSION-linux-$ARCH.tar.xz" -C /usr/local --strip-components=1 --no-same-owner \
&& rm "node-v$NODE_VERSION-linux-$ARCH.tar.xz" SHASUMS256.txt.asc \
&& ln -s /usr/local/bin/node /usr/local/bin/nodejs
# Installing gradle
ENV GRADLE_VERSION 3.3
RUN mkdir /opt/gradle \
&& wget https://services.gradle.org/distributions/gradle-${GRADLE_VERSION}-bin.zip \
&& unzip -d /opt/gradle gradle-${GRADLE_VERSION}-bin.zip
ENV GRADLE_HOME /opt/gradle/gradle-${GRADLE_VERSION}/bin
ENV PATH $PATH:$GRADLE_HOME
When using this docker image; 使用此docker映像时； the docker container comes up and I am able to access the gradle correctly. docker容器出现，我能够正确访问gradle。 However when invoking the above ionic cordova build command after installing cordova7 we get a detailed error message : Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed . The detailed error message is follows : 但是，在安装cordova7之后调用上述离子式cordova build命令时，我们会收到一条详细的错误消息： Gradle build守护进程意外消失（它可能已被杀死或崩溃了 。详细的错误消息如下：
FAILURE: Build failed with an exception.
- What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) * Try: Run with --stacktrace option to get the stack trace.
[ERROR] An error occurred while running cordova build android --debug --release --buildConfig (exit code 1).
We tried using latest gradle build version 4.6 and the problem persist and the gradle daemon gets killed immediately. 我们尝试使用最新的gradle构建版本4.6，但问题仍然存在 ，并且gradle守护程序立即被杀死。 Some of the gradle logs thats gets printed in the concourse ci : 一些gradle日志thats被打印在大厅ci中：
cordova build android --debug --release --buildConfig
You have been opted out of telemetry.
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 Reading build config file: /tmp/build/80754af9/source/build.json Reading the keystore from: /tmp/build/80754af9/source/Elsa2Go_android.keystore Starting a Gradle Daemon (subsequent builds will be faster) The message received from the daemon indicates that the daemon has disappeared.
Build request sent: Build{id=a31854f5-a2c8-4248-b580-2ae398dbba4c.1, currentDir=/tmp/build/80754af9/source} Attempting to read last messages from the daemon log... Daemon pid: 731 log file: /root/.gradle/daemon/3.3/daemon-731.out.log
----- Last 20 lines from daemon log file - daemon-731.out.log ----- 10:01:27.698 [DEBUG] [org.gradle.launcher.daemon.bootstrap.DaemonStartupCommunication] Completed writing the daemon greeting.
10:01:27.795 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] stopOnExpiration() called on daemon 10:01:27.799 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] awaitExpiration() called on daemon 10:01:27.800 [DEBUG] [org.gradle.internal.remote.internal.inet.TcpIncomingConnector] Accepted connection from /127.0.0.1:54152 to /127.0.0.1:45644.
10:01:27.801 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] daemon is running.
10:01:27.950 [DEBUG] [org.gradle.launcher.daemon.server.DefaultDaemonConnection] thread 14: Received non-IO message from client: Build{id=a31854f5-a2c8-4248-b580-2ae398dbba4c.1, currentDir=/tmp/build/80754af9/source} 10:01:27.951 [INFO] [org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler] Received command: Build{id=a31854f5-a2c8-4248-b580-2ae398dbba4c.1, currentDir=/tmp/build/80754af9/source}.
10:01:27.957 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
PS : Version information PS：版本信息
- "ionic": "3.19.0" “ ionic”：“ 3.19.0”
- "@angular/cli": "1.5.3" “ @ angular / cli”：“ 1.5.3”
- Android plaftorm : installed in ionic Android plaftorm：安装在离子型
Approaches tried but same issue was observed : 尝试了方法，但观察到相同的问题：
- Setting the gradle daemon as false in gradle properties by : org.gradle.daemon=false 通过以下 方式 在gradle属性中将gradle守护进程设置为false： org.gradle.daemon = false
- Setting the heap size to a mininum in gradle properties by : org.gradle.jvmargs=-XX:MaxPermSize=256m -Xms256m -Xmx512m 通过以下 方式 在gradle属性中将堆大小设置为最小值： org.gradle.jvmargs = -XX：MaxPermSize = 256m -Xms256m -Xmx512m
- Using latest version of gradle 4.6 使用最新版本的Gradle 4.6
Any idea / suggestions as to what is the root cause will be of great help. 关于根本原因的任何想法/建议都会有很大帮助。 Thanks in advance. 提前致谢。
1 个解决方案
解决方案1
0 2018-03-15 17:24:04
What happens, if you remove the --no-daemon from the args? 如果从args中删除--no-daemon，会发生什么？ I mean Gradle says that the preferred way is the deamon since Gradle 3.0 ( https://docs.gradle.org/current/userguide/gradle_daemon.html#sec:disabling_the_daemon ). 我的意思是Gradle说，自Gradle 3.0（ https://docs.gradle.org/current/userguide/gradle_daemon.html#sec:disabling_the_daemon ）以来，首选方式是守护进程。 Furthermore you don't have a need for it, because Docker provides you a fresh environment. 此外，您不需要它，因为Docker为您提供了全新的环境。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.