travis-ci

Is there a way to only run a specific set of tests in an Android Gradle project?

你说的曾经没有我的故事 提交于 2019-11-28 11:27:15
I have an Android/Gradle project. Whenever I want to run tests, I run: ./gradlew connectedInstrumentTest which runs all my tests under the test folder of my project. My test folder has several automation tests as well as non-automation tests. I'm mostly interested in running the fast non-automation tests without the slow automation tests. Is there a way to run just a specific set of tests, such as from one specific class or anything similar? I'm basically asking about any kind of separation so that I can choose to run just a few tests when I want to. Created a sample project here . Edit local

Travis reports odd message of corrupted Gemfile.lock

随声附和 提交于 2019-11-28 11:22:26
Im using bundler to install stuff and since I have added Gemfile.lock , travis started to complain with: Your Gemfile.lock is corrupt. The following gem is missing from the DEPENDENCIES section: 'echoe' Of course, everything works locally. It also works using DeployBot . I even installed docker ubuntu and tried, still ok. My Gemfile.lock is not corrupt. Same versions of ruby and bundler is used. What is going on? Update This is something related to bundler version. Im using 1.11.0, but got reports that it worked with eg. 1.8.3. ?? s01ipsist We've seen a very similar issue today on Buildkite

How to ensure that README.rst is valid?

久未见 提交于 2019-11-28 11:19:51
There are two version of my little tool: https://pypi.python.org/pypi/tbzuploader/2017.11.0 https://pypi.python.org/pypi/tbzuploader/2017.12.0 Bug: The pypi page looks ugly. In the last update a change in README.rst cases a warning: user@host> rst2html.py README.rst > /tmp/foo.html README.rst:18: (WARNING/2) Inline emphasis start-string without end-string. README.rst:18: (WARNING/2) Inline emphasis start-string without end-string. Now the pypi page looks ugly :-( I use this recipe to do CI, bumpversion, upload to pypi: https://github.com/guettli/github-travis-bumpversion-pypi How could I

Create an emulator with a decent size from command line

*爱你&永不变心* 提交于 2019-11-28 04:47:01
问题 I want to create an ARM API 21 emulator loaded with Google APIs. Here's how I create the AVD: ANDROID_ABI=google_apis/armeabi-v7a EMULATOR_VERSION=21 avd --force -n nexus4-emulator -t "Google Inc.:Google APIs:"$EMULATOR_VERSION --abi $ANDROID_ABI --device "Nexus 4" -c 128M And now I start up the emulator with: emulator -avd nexus4-emulator & However, this is what I get: a screen with tiny dimensions (in terms of effective pixels): How can I change this config so that I have a properly sized

Committing via travis ci failing

孤街浪徒 提交于 2019-11-28 04:42:47
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 for 'https://github.com/tusharmath/tusharm.com.git/' Use --force to continue. Aborted due to warnings.

How to make travis execute Angular tests on Chrome (“Please set env variable CHROME_BIN”)

我们两清 提交于 2019-11-28 04:40:14
I'm working on a sample Angular project generated by yeoman. I am able to run karma tests locally (I set system variable CHROME_BIN to point to chromium binary, but this could have been done in more elegant way. Just a quick work-around.) However, when attempting to produce a successful build with travis, I get following error: ERROR [launcher]: Cannot start Chrome Can not find the binary google-chrome Please set env variable CHROME_BIN I've followed the steps described here (basically using generator-travis-ci ) Then tried to fix it with this - got another error: /home/travis/build.sh: line

How to find the current git branch in detached HEAD state

让人想犯罪 __ 提交于 2019-11-28 04:20:06
I can find the current git branch name by doing either of these: git branch | awk '/^\*/ { print $2 }' git describe --contains --all HEAD But when in a detached HEAD state, such as in the post build phase in a Jenkins maven build (or in a Travis git fetch), these commands doesn't work. My current working solution is this: git show-ref | grep $(git log --pretty=%h -1) | sed 's|.*/\(.*\)|\1|' | sort -u | grep -v HEAD It displays any branch name that has the last commit on its HEAD tip. This works fine, but I feel that someone with stronger git-fu might have a prettier solution? A more porcelain

Why is python setup.py saying invalid command 'bdist_wheel' on Travis CI?

北慕城南 提交于 2019-11-28 03:52:23
My Python package has a setup.py which builds fine locally on Ubuntu Trusty and on a fresh Vagrant Ubuntu Trusty VM when I provision it like this: sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7 sudo -H pip install setuptools wheel virtualenv --upgrade But when I do the same on a Travis CI Trusty Beta VM: - sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken - curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7 -

How to publish artifacts in Travis CI?

扶醉桌前 提交于 2019-11-28 03:47:56
I would like to use Travis CI for my open-source project. The issue that Travis doesn't provide any ways to publish produced artifacts (though, they have this in their future plans). What are workarounds to publish/upload artifacts somewhere? I'm allowed to execute any scripts on a CI machine. Simple upload will work, but there is security issue: anyone will be able to upload something in the same way as all sources are public. The "github releases uploading" feature is announced recently. It officially supports everything that is needed. See http://docs.travis-ci.com/user/deployment/releases/

How to reproduce a travis-ci build environment for debugging

雨燕双飞 提交于 2019-11-28 03:22:46
I am seeing a build failure on travis-ci, which I cannot reproduce on my local machine. Are there instructions somewhere for setting up a VM that is identical to the travis-ci linux build environment? I'm glad to have travis-ci already reveal a new bug, but less excited to debug it by sending in commits that add debug code. eregon For container-based builds, there are now instructions on how to setup a docker image locally . Unfortunately, quite a few steps are still manual. Here are the commands you need to get it up and running: # change the image according to the language chosen in .travis