If you check out the travis-ci status page (http://www.traviscistatus.com/) you’ll notice that the “Active Linux Builds for Open Source projects” periodically maxes out. Based on how the travis private build system works (a single queue for all “Build Jobs” with no more than x running at a time), I suspect they have a single queue … Read more
Travis-CI’s cron jobs feature was implemented in May 2016.
Use this solution to get it running using the preinstalled Chromium Version in Travis-CI VM: https://github.com/karma-runner/karma/issues/1144#issuecomment-53633076 .travis.yml node_js: – “0.10” script: node_modules/karma/bin/karma start test/karma.conf.js –single-run before_install: – export CHROME_BIN=chromium-browser – export DISPLAY=:99.0 – sh -e /etc/init.d/xvfb start karma.conf.js module.exports = function(config) { var configuration = { /* … */ // start these browsers browsers: [‘Chrome’, … Read more
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 + … Read more
I noticed caching the node_modules folder caused problems (build fails) while caching the .npm cache avoided it. I believe it’s because the .npm cache doesn’t store compiled native modules while the node_modules folder does. So when you test different versions of node, as is common in Travis-CI, it will try to load a native module … Read more
There is now a better way to do this. sudo: false dist: trusty language: cpp os: – linux compiler: – gcc – clang install: # /usr/bin/gcc is 4.6 always, but gcc-X.Y is available. – if [[ $CXX = g++ ]]; then export CXX=”g++-4.9″ CC=”gcc-4.9″; fi # /usr/bin/clang has a conflict with gcc, so use clang-X.Y. … Read more
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 logs would be useful … Read more
You don’t have 32 lines in your file (probably because you stripped non-essential data out of the example), but the indentation level points to the line with fi. Actually the problem starts earlier and what you want to do is specify the action to take as a multi-line string. You can specify those in YAML … Read more