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
node_js:
- "0.10"
before_install:
- "curl -L https://git.io/ejPSng | /bin/sh"
env:
- CXX=g++-4.8
addons:
apt:
sources:
- ubuntu-toolchain-r-test
packages:
- g++-4.8UPDATE (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 https://travis-ci.org with Github and navigate to https://travis-ci.org/profile
Enable travis support for your project listed there.
You can configure tests with two environment variables:
WORKING_DIR-- working directory to runmeteorfromPACKAGES-- list of package names or directories to test, separated by;, by default./; specfiy empty string to test all packagesTEST_COMMAND-- you can specify a custom command to run, instead of defaultmeteor, it gets all the argumentsmeteorwould; this is useful if you want to do some more pre- or post-processingMETEOR_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 travis.sh (name not important):
#!/bin/sh
meteor "$@" --settings test/settings.travis.jsonAdd the following environment variable to your .travis.yml:
env: TEST_COMMAND=./travis.shBe sure to set the executable flag on your new script:
$ chmod +x travis.shSee here for more information
