travis-ci

问题 $ ./build.sh --quiet verify /home/travis/build.sh: line 59: ./build.sh: Permission denied. The command "./build.sh --quiet verify" exited with 126. 回答1: Looks like you need to check in the file build.sh with execution permissions. Please try the following from your own machine: git update-index --add --chmod=+x build.sh git commit -m 'Make build.sh executable' git push 回答2: You can grant the needed permission by adding this lines to the .travis.yml before_install: - chmod +x build.sh 回答3: Run

问题 I am facing warning statements in my travis builds. Warning: This development build of composer is over 30 days old. It is recommended to update it by running "/home/travis/.phpenv/versions/5.3.26/bin/composer.phar self-update" to get the latest version. How do I then run this? See an e.g. here 回答1: It is not such a good idea to hard-code the php path as paths might change when Travis gets update. I suggest simply calling composer self-update 回答2: inside your travis.yml make sure you have

问题 I'm trying to update an Android project from using the API Level 19 SDK and build tools to the newest API Level 21, including the Google APIs. Everything was running fine on Travis prior to this update (for example, see this build). When I run with the new API level I see the following error: 0.42s$ echo no | android create avd --force -n test -t "Google Inc.:Google APIs:"$ANDROID_API_LEVEL --abi $ANDROID_ABI Valid ABIs: no ABIs. Error: Invalid --abi armeabi-v7a for the selected target. The

问题 I have a rails project and am running tests for my JavaScript test (Jasmine) through Karma .travis.yml file language: ruby rvm: - 2.0.0 script: - RAILS_ENV=test bundle exec rake --trace db:migrate test - karma start --single-run --browsers PhantomJS test/karma/config/unit.js Travis fails saying it does not find karma. is there a way to define node_js as another language and install karma on the build VM? 回答1: It is not possible yet to have several languages on travis configuration file. On

问题 I have a rails project and am running tests for my JavaScript test (Jasmine) through Karma .travis.yml file language: ruby rvm: - 2.0.0 script: - RAILS_ENV=test bundle exec rake --trace db:migrate test - karma start --single-run --browsers PhantomJS test/karma/config/unit.js Travis fails saying it does not find karma. is there a way to define node_js as another language and install karma on the build VM? 回答1: It is not possible yet to have several languages on travis configuration file. On

问题 Travis CI continuous integration service officially supports many languages, but not C# or F#. Can I use it with my .net projects? 回答1: Travis CI now supports C#. Quoting liberally from that page: Overview The setup for C#, F#, and Visual Basic projects looks like this: language: csharp solution: solution-name.sln mono: - latest - 3.12.0 - 3.10.0 Script By default Travis will run xbuild solution-name.sln. Xbuild is a build tool designed to be an implementation for Microsoft's MSBuild tool. To

问题 I want to use apt to install some packages for the test, however, it fails due to that the sudo is disabled. I found the following in the test output: Sudo, the FireFox addon, setuid and setgid have been disabled. It seems that the output comes from this line in travic-ci, but setting paranoid_mode to false in .travis.yml does not work. How to enable sudo access? PS: I am using private repo. EDIT: The following .travis.yml will fail due to sudo: must be setuid root when running sudo apt-get

问题 I am trying to use grunt-gh-pages extension to commit to my gh-branch. It works fine locally but when I use TRAVIS-CI it fails. It gives the following error message - Warning: fatal: remote error: You can't push to git://github.com/tusharmath/tusharm.com.git Use https://github.com/tusharmath/tusharm.com.git Use --force to continue. And when I update the repo option I get the following error - Warning: remote: Anonymous access to tusharmath/tusharm.com.git denied. fatal: Authentication failed

问题 I'm regularily using Travis CI and noticed multiple issues with forked projects the last weeks when building on Travis which do not occur locally or on the Travis instance of the forked project. I made sure that I used the the same Maven version which imo is all that can be different from the Travis CI environment since both Maven and Java are portable across platforms. Travis runs Ubuntu 12.04 or 14.04 which I do as well (17.04). In detail I experienced: The failure to retrieve a SNAPSHOT

问题 I'm regularily using Travis CI and noticed multiple issues with forked projects the last weeks when building on Travis which do not occur locally or on the Travis instance of the forked project. I made sure that I used the the same Maven version which imo is all that can be different from the Travis CI environment since both Maven and Java are portable across platforms. Travis runs Ubuntu 12.04 or 14.04 which I do as well (17.04). In detail I experienced: The failure to retrieve a SNAPSHOT