为什么特拉维斯CI杀死我的脚本的进程? [英] Why does Travis CI kill the process for my script?
问题描述
我添加了以下配置上的特拉维斯CI =https://开头github上。 COM / johnjohndoe / CampFahrplan相对=nofollow> Fahrplan Android项目:
语言:机器人机器人:
组件: #所有构建系统组件应该是最新版本
# - 工具
# - 平台工具
- 构建工具 - 21.1.1
- Android的19
- sysimg-19
- 加上
- 额外的 #我们不能从Maven的中央或类似中得到的库
- 超Android的支持
- 超Android的m2repositoryJDK:
- oraclejdk7
- openjdk7通知:
电子邮件:真before_script:
- 搭配chmod + X gradlew
- MV应用程序/应用gradle.properties.example / gradle.properties脚本:
- ./gradlew干净assembleDebug
由于某些原因,过程被一再打死可以在建置沿革可见一>。它停在不同的位置。该错误消息不是信息:
./gradlew干净assembleDebug137退出命令
块引用>解决方案只有检查gradle这个版本,你可以强制下载之前运行的脚本(帮助我避免错误137),但现在我使用
包装
的gradle如此,wrapper.jar被更新。如果它不工作,你可以尝试下载Android的依赖之前,之前也运行脚本和清洁。
我认为他们不会在默认情况下组装,但我喜欢覆盖安装阶段,可以肯定的。
在我的情况下,错误137是由于并发性(建立/仿真器)和就业特拉维斯慈杀害。我解决它做这类型的变化,我不明白,这非常好。
语言:机器人JDK:
- oraclejdk7
- openjdk7机器人:
组件: #所有构建系统组件应该是最新版本
- 工具
- 平台工具
- 构建工具 - 21.1.1
- Android的19 #我们不能从Maven的中央或类似中得到的库
- 超Android的支持
- 超Android的m2repository
通知:
电子邮件:真before_install:
默认情况下启用#禁用服务
#http://docs.travis-ci.com/user/database-setup/#MySQL
- 须藤/etc/init.d/mysql停止
- 须藤/etc/init.d/postgresql的停
#以下没有工作可靠
# - 须藤服务mysql的停止
# - 须藤服务一条龙的PostgreSQL安装:
#确保摇篮包装是可执行的,下载包装和展示版本
- 搭配chmod + X ./gradlew; ls -l命令gradlew; ./gradlew包装-v
#下载并显示Android的依赖
# - ./gradlew androidDependenciesbefore_script:
#确保签约配置是present
- MV应用程序/应用gradle.properties.example / gradle.properties脚本:
- ./gradlew干净assembleDebugI added the following configuration to run Travis CI on the Fahrplan Android project:
language: android android: components: # All the build system components should be at the latest version # - tools # - platform-tools - build-tools-21.1.1 - android-19 - sysimg-19 - add-on - extra # The libraries we can't get from Maven Central or similar - extra-android-support - extra-android-m2repository jdk: - oraclejdk7 - openjdk7 notifications: email: true before_script: - chmod +x gradlew - mv app/gradle.properties.example app/gradle.properties script: - ./gradlew clean assembleDebug
For some reason the process gets killed again and again as can be seen in the build history. It stops at different locations. The error message is not that informative:
The command "./gradlew clean assembleDebug" exited with 137
解决方案Only checking the gradle version you can force the download before you run the script (helps me to avoid error 137) but now i use
wrapper
so gradle-wrapper.jar is updated.If it doesn't work, you can try to download the android dependencies before to run the script and clean before too.
I think they don't assemble by default but I like to override install stage to be sure.
In my case, error 137 is due concurrency (build/emulator) and jobs killed by Travis-ci. I solve it doing changes of this type and I don't understand it very well.
language: android jdk: - oraclejdk7 - openjdk7 android: components: # All the build system components should be at the latest version - tools - platform-tools - build-tools-21.1.1 - android-19 # The libraries we can't get from Maven Central or similar - extra-android-support - extra-android-m2repository notifications: email: true before_install: # Disable services enabled by default # http://docs.travis-ci.com/user/database-setup/#MySQL - sudo /etc/init.d/mysql stop - sudo /etc/init.d/postgresql stop # The following did not work reliable # - sudo service mysql stop # - sudo service postgresql stop install: # Ensure Gradle wrapper is executable, download wrapper and show version - chmod +x ./gradlew; ls -l gradlew; ./gradlew wrapper -v # Download and show android dependencies # - ./gradlew androidDependencies before_script: # Ensure signing configuration is present - mv app/gradle.properties.example app/gradle.properties script: - ./gradlew clean assembleDebug
这篇关于为什么特拉维斯CI杀死我的脚本的进程?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!