该分支以前是功能性的,然后合并为主,并且在主上的构建失败。主人被恢复,然后将主人合并到该分支中,并进行了一些修复。当尝试合并回主时,构建再次失败了以下错误。推动通过,PR失败。
* What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not find com.squareup.leakcanary:leakcanary-android:1.5.4.
travis.yml文件:
sudo: false
language: android
android:
components:
- build-tools-27.0.2
- android-27
- sys-img-armeabi-v7a-android-27
jdk:
- oraclejdk8
before_install:
- yes | sdkmanager "platforms;android-27"
- chmod +x gradlew
#First app is built then unit tests are run
jobs:
include:
- stage: build
async: true
script: ./gradlew assemble
- stage: test
async: true
script: ./gradlew -w runUnitTests
notifications:
email:
recipients:
- email@me.com
on_success: always # default: change
on_failure: always # default: always
我今天感觉到了Maven Repo中断,并且面临同样的问题。几个小时后,我发现失败的Travis工作现在正常工作。在您身边检查一下。
此外,对于任何给定的方案,当缺少类Path的情况时,应该检查build.gradle
文件而不是.travis.yml
文件。
失败消息说app:debugCompileClasspath
任务在寻找com.squareup.leakcanary:leakcanary-android:1.5.4
(JAR或AAR(时失败。gradle允许您在根级别定义存储库
allProjects{
repositories {
maven() //Gradle has definition the points to https://jcenter.bintray.com/
}
}
因此,它将查看类文件或JAR文件的以下位置。
Name: $ANDROID_HOME/extras/m2repository; url: file:/$ANDROID_HOME/extras/m2repository/
Name: $ANDROID_HOME/extras/google/m2repository; url: $ANDROID_HOME/extras/google/m2repository/
Name: $ANDROID_HOME/extras/android/m2repository; url: file:$ANDROID_HOME/extras/android/m2repository/
Name: BintrayJCenter; url: https://jcenter.bintray.com/
如果找不到依赖项分辨率,将失败。