unleash.unleash/.travis.yml

sudo: false
language: node_js
node_js:
- "0.10"
env: TEST_DATABASE_URL=postgres://postgres@localhost:5432/unleash_test
before_script:
- echo '--timeout 10000' > test/mocha.opts
- psql -c 'create database unleash_test;' -U postgres
- 'DATABASE_URL=$TEST_DATABASE_URL ./node_modules/.bin/db-migrate up'
script:
- npm install
- npm test
- npm run coverage-report || true
notifications:
  hipchat:
    rooms:
      secure: GiIDk52xccnUKnevjLE+w6eUXg0jfV7oOmagw5VnOV5jXGUxdzMk/Q9um+oSClEPE51IvF76zoFEKPIX/CNdjgalEr+CZADy1gene/YRGrNgrXmYYmiU1/dNzelpla1WpKPrY2pkbOgKxrCR9ScID+pMs6vzvJnPwK9vu66W61U=
addons:
  postgresql: "9.4"
Using Travis new container-based stack 2014-12-18 10:05:02 +01:00			`sudo: false`
Fix .travis.yml 2014-10-31 16:36:42 +01:00			`language: node_js`
Failure to report coverage should not cause build failure. 2014-11-10 16:34:20 +01:00			`node_js:`
Fix .travis.yml 2014-10-31 16:36:42 +01:00			`- "0.10"`
Use TEST_DATABASE_URL for running test against a separate DB. 2014-12-12 14:11:09 +01:00			`env: TEST_DATABASE_URL=postgres://postgres@localhost:5432/unleash_test`
Bump mocha timeout on Travis 2014-11-12 15:15:23 +01:00			`before_script:`
			`- echo '--timeout 10000' > test/mocha.opts`
Begin work on running tests against the database: * Add Travis postgresql setup. * Replace "db mocks" with a before hook that creates the same data through the HTTP API. * Reset DB and re-create all fixtures for each test. We'll need something better here. * CAVEAT: no concept of a dev vs test database. Running tests will clear data from the currently configured database. 2014-12-05 17:20:17 +01:00			`- psql -c 'create database unleash_test;' -U postgres`
Fix DB url in Travis migration 2014-12-12 16:17:53 +01:00			`- 'DATABASE_URL=$TEST_DATABASE_URL ./node_modules/.bin/db-migrate up'`
A bit of a hack to support java and node. [1] claims that node.js is available in all envs in travis. This setup is not optimal as we now longer controll the node version, but could work for now. [1] http://stackoverflow.com/questions/18456611/is-it-possible-to-set-up-travis-to-run-tests-for-several-languages 2014-10-21 08:42:36 +02:00			`script:`
Failure to report coverage should not cause build failure. 2014-11-10 16:34:20 +01:00			`- npm install`
			`- npm test`
			`- npm run coverage-report \|\| true`
Add HipChat notifications 2014-09-30 19:43:15 +02:00			`notifications:`
			`hipchat:`
			`rooms:`
			`secure: GiIDk52xccnUKnevjLE+w6eUXg0jfV7oOmagw5VnOV5jXGUxdzMk/Q9um+oSClEPE51IvF76zoFEKPIX/CNdjgalEr+CZADy1gene/YRGrNgrXmYYmiU1/dNzelpla1WpKPrY2pkbOgKxrCR9ScID+pMs6vzvJnPwK9vu66W61U=`
Begin work on running tests against the database: * Add Travis postgresql setup. * Replace "db mocks" with a before hook that creates the same data through the HTTP API. * Reset DB and re-create all fixtures for each test. We'll need something better here. * CAVEAT: no concept of a dev vs test database. Running tests will clear data from the currently configured database. 2014-12-05 17:20:17 +01:00			`addons:`
Testing out Postgres 9.4 on Travis [experimental] http://docs.travis-ci.com/user/build-environment-updates/2015-02-03/#PostgreSQL-9.4 2015-02-10 18:07:37 +01:00			`postgresql: "9.4"`