travis-ci

I want to kick off an npm deployment when a tag, that looks like a semantic version, is pushed, e.g. v1.2.3 . I see that the tag name is in the TRAVIS_TAG environment variable and that I can specify an on: condition, which "can be any Bash condition". I have no idea what to write here and how to debug it. - provider: npm on: tags: true all_branches: true condition: ??? Ideally, I would like to not bother with Bash at all - I would like the condition to execute a Node.js script and then decide whether to deploy or not depending on the node exit code. How can I do that? Simplest way would still

For my builds on Travis, I want to be able to read the test results when there are failing tests to see the stacktrace of those failing tests. Currently, these reports are stored locally on the machine that runs the tests, so I am not able to access the local files where the reports are. I also don't want to archive these files through Amazon S3 because that seems like way too much of a hassle. Something like : How to get surefire reports form Travis-CI build? seems like it could work, but also seems complicated. Basically, I want to be able to read a local test result file from Travis without

I am attempting to setup Travis CI so that it runs instrumentation tests on an emulator running API 25. Travis runs the tests to completion on API 4/10/19, but fails to startup the emulator for API 25, with the following message: $ echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI Valid ABIs: no ABIs. Error: Invalid --abi armeabi-v7a for the selected target. The output of android list targets shows that the API 19 emulator has a Tag/ABI, whereas the API 25 emulator does not: id: 7 or "android-19" Name: Android 4.4.2 Type: Platform API level: 19 Revision: 4

I am having trouble getting chromedriver on Travis-CI working for my project knockout-secure-binding . I am trying to use WebdriverJS to automate testing with Chrome, at the least. I noted that there seems to be some issues with chromedriver on Travis-CI, including: http://github.com/travis-ci/travis-ci/issues/938 http://github.com/travis-ci/travis-ci/issues/272 https://code.google.com/p/chromedriver/issues/detail?id=308 The issue seems to be a variant of "chrome not reachable", and from what I can gather it requires an upstream engagement by Google to fix it. The details of the error are

Is there a way to tell Travis CI (or another continuous integration service) to test the package on different operating systems? Working with the filesystem, and it would be great to double-check it's all platform-agnostic. Update 3 Windows support has been released! You can now use Travis CI with Linux, macOS, and Windows. You can find their blog post about it here . Update 2 This feature is enabled now (no need to send request to Travis team). Though still considered beta: Multi-OS Works fine for me, here is Linux + OSX configuration: .travis.yml build matrix Windows support still in

How do you test different Python versions with Tox from within Travis-CI ? I have a tox.ini : [tox] envlist = py{27,33,34,35} recreate = True [testenv] basepython = py27: python2.7 py33: python3.3 py34: python3.4 py35: python3.5 deps = -r{toxinidir}/pip-requirements.txt -r{toxinidir}/pip-requirements-test.txt commands = py.test which runs my Python unittests in several Python versions and works perfectly. I want to setup a build in Travis-CI to automatically run this when I push changes to Github, so I have a .travis.yml : language: python python: - "2.7" - "3.3" - "3.4" - "3.5" install: - pip

One used to be able to download Vagrant boxes to debug Travis builds (for GitHub projects for instance). Apparently, this is no longer possible, so how do people currently debug complex Travis build chains locally? One way to inspect the build (not to debug, sorry) is to send the build logs to another server on failure. Here is an example: after_failure - sudo tar -czf /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz your-application-logs/ - scp /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz travis@your-server.com:~/logs You could send them via email, store them on a storage server or whatever. These

I'm using Travis-CI to provide continuous integration builds for a few Java open source projects I'm working on. Normally this works smoothly, but I have a problem when the POM specifies GPG signing, e.g. <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-gpg-plugin</artifactId> <version>1.4</version> <executions> <execution> <id>sign-artifacts</id> <phase>verify</phase> <goals> <goal>sign</goal> </goals> </execution> </executions> </plugin> This causes the Travis build to fail - apparently because it does not have a passphrase available while running mvn install . See this