travis-ci

travis-ci build keeps failing with ShellCommandUnresponsiveException

由 橙三吉。 提交于 2019-11-30 08:40:19
问题 I'm trying to get travis-ci to work with my android application. If I only execute assembleDebug it works fine. But I want to run tests too and generate code coverage. This is the config I have right now: language: android android: components: # Uncomment the lines below if you want to # use the latest revision of Android SDK Tools - platform-tools - tools # The BuildTools version used by your project - build-tools-23.0.1 # The SDK version used to compile your project - android-23 #

Get Travis Shield on Github to Reflect Selected Branch Status

由 空扰寡人 提交于 2019-11-30 07:03:30
Right now I can get my travis shield to either reflect the latest run, or a specific branch, irrespective of what branch I select in my github project page. I can do this by either leaving out or specifying the branch name at the end of the URL. Instead, I would like to get the shield corresponding to the selected branch. In other words, each time I select a different branch, the URL to the travis shield in my README.md file would change. In SVN you could use SVN keywords to implement something of the sort by modifying the shield URL with the branch name (or something like it). This QA

Travis-CI Android SDK license problems

由 断了今生、忘了曾经 提交于 2019-11-30 05:40:32
问题 I'm trying to build my Android project with Travis and currently I'm getting error: A problem occurred configuring project ':app'. > You have not accepted the license agreements of the following SDK components: [Android SDK Build-Tools 27.0.1]. I don't know how, but yesterday I could solve problem with that: before_install: - yes | sdkmanager "platforms;android-27" But now it doesn't help me. I will be grateful for any advice. Here is build URL https://travis-ci.org/madsunrise/luna-mobile

Using R package source files in packrat (rather than CRAN) with Travis-CI

由 旧街凉风 提交于 2019-11-30 05:09:12
I'm working with an R package that is an RStudio project , and I'm using packrat to keep a local copy of the source of the packages I depend on for my project. I've got Travis-CI checking my R package each time I make a commit, but each time Travis builds my package it gets the latest version of the dependent packages, rather than the versions I've got in my packrat/ directory. I can see in richfitz/wood that he appears to have achieved this goal with this in his .travis.yml file: env: USE_PACKRAT=1 and a fairly complex make/packrat.mk file which makes it all work. My question is what is the

Error using Travis CI with Sonarcloud: Not authorized. Please check the properties sonar.login and sonar.password

由 流过昼夜 提交于 2019-11-30 05:02:45
问题 I'm following Get started instructions on sonarcloud.io to execute the SonarQube Scanner for Maven from my computer: mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent package sonar:sonar \ -Dsonar.host.url=https://sonarcloud.io \ -Dsonar.organization=ron190-github \ -Dsonar.login=9...e Manual execution is working: [INFO] ANALYSIS SUCCESSFUL, you can browse https://sonarcloud.io/dashboard/index /jsql-injection:jsql-injection But when I'm ready to automate with Travis CI it's failing with

Travis CI ignoring MAVEN_OPTS?

由 时光怂恿深爱的人放手 提交于 2019-11-30 03:45:14
问题 My Scala project (Maven-managed) is failing to build on Travis, throwing a GC overhead limit exceeded error despite compiling fine locally with the same MAVEN_OPTS=-Xmx3g -XX:MaxPermSize=512m . I suspect that Travis is somehow ignoring my MAVEN_OPTS : When I try to test against Oracle JDK 8, Travis logs: $ Setting environment variables from .travis.yml $ export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx3g" which looks good. However, soon after it logs: Java HotSpot(TM) 64-Bit Server VM warning:

Add secret environment variable to Travis CI

由 柔情痞子 提交于 2019-11-30 03:13:20
问题 I'm currently trying to add a secret environment variable to Travis-CI. In the docs ("Secure environment variables") I found the following line to do this: gem install travis travis encrypt -r travis-ci/travis-core MY_SECRET_ENV=super_secret If I understood this correctly I must replace travis-ci/travis-core with the name of my own repository, because the encryption should only be valid for my repository. Therefore, there must be a public key in the repository. Is there a special travis

How to add my module to travis-ci pythonpath

由 心不动则不痛 提交于 2019-11-30 02:33:31
问题 I'm setting up Travis-CI for my project, and oddly, I can't import my project: $ python tests/tests.py Traceback (most recent call last): File "tests/tests.py", line 11, in <module> from my_module.lib.importer import build_module_list ImportError: No module named my_module.lib.importer In production, I just create a symlink like so: sudo ln -s /usr/local/my_module /usr/lib/python2.7/dist-packages/my_module But I don't know -- or want to know, really -- Travis-CI's folder structure. This seems

Travis CI build doesn't work with Android Constraint Layout

由 社会主义新天地 提交于 2019-11-30 01:43:20
I am trying to make Travis build my Android project. It fails when it tries to download the library for ConstraintLayout . Do you know what I have to do to make it work? My .travis.yml is this: language: android jdk: - oraclejdk8 android: components: - platform-tools - tools - build-tools-23.0.2 - android-23 - extra-android-support - extra-android-m2repository - extra-google-m2repository My build.gradle is: apply plugin: 'com.android.application' android { compileSdkVersion 23 buildToolsVersion "23.0.2" defaultConfig { applicationId "my.example.bdd" minSdkVersion 9 targetSdkVersion 23

The bundle UITests couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle

由 心已入冬 提交于 2019-11-29 21:13:45
I can't run my test case due to this following errors : The bundle “UITests” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle. Library not loaded: @rpath/Alamofire.framework/Alamofire. Reason: image not found Try searching and solving since two days but couldn't get through this issue can someone please help. I was able to reproduce this issue with the project generated by Xcode 10.1. I used Swift 4.2 and CocoaPods as a dependency manager. I had the following Podfile: # Uncomment the next line to define a global platform for your project
订阅 travis-ci