Travis CI support for Meteor (Smart) Packages
JavaScript Shell Makefile
Latest commit dca8e51 Aug 17, 2016 2 @arunoda committed on GitHub Merge pull request #45 from mitar/brcrypt
To compile bcrypt on Meteor 1.4
Failed to load latest commit information.
example-package added example package Jun 17, 2013
.travis-sample.yml To compile bcrypt on Meteor 1.4. Aug 16, 2016
Makefile Makefile updated with the JS file Jun 5, 2013 removing mrt update Oct 26, 2014
phantom_runner.js Updated PhantomJS runner with one from Meteor 0.6.5. Aug 22, 2013


Travis CI support for Meteor (Smart) Packages

Add following file to your meteor package as .travis.yml

## Add this file to your meteor package as `.travis.yml`

sudo: required
language: node_js
  - "0.10"

  - "curl -L | /bin/sh"

  - CXX=g++-4.8
      - ubuntu-toolchain-r-test
      - g++-4.8

UPDATE (2015/03/31) : Please note that the latest version of .travis.yaml now includes "sudo: required" to cope with new permissions constraints in Travis virtual machines.

UPDATE (2016/08/16) : The latest version of .travis.yaml now includes a compiler to compile the bcrypt NPM module.

Login to with Github and navigate to

Enable travis support for your project listed there.

Meteor Cluster - Travis Support

You can configure tests with two environment variables:

  • WORKING_DIR -- working directory to run meteor from
  • PACKAGES -- list of package names or directories to test, separated by ;, by default ./; specfiy empty string to test all packages
  • TEST_COMMAND -- you can specify a custom command to run, instead of default meteor, it gets all the arguments meteor would; this is useful if you want to do some more pre- or post-processing
  • METEOR_RELEASE -- you can specify the meteor release to run the tests with.

If you would like to specify more arguments (such as --settings), create a simple shell script and pass the path to TEST_COMMAND.

Create the following (name not important):

meteor "$@" --settings test/settings.travis.json

Add the following environment variable to your .travis.yml:


Be sure to set the executable flag on your new script:

$ chmod +x

See here for more information