unleash.unleash/.travis.yml

sudo: false
language: node_js
node_js:
- "6"
env:
- DATABASE_URL=postgres://postgres@localhost:5432/unleash_test TEST_DATABASE_URL=postgres://postgres@localhost:5432/unleash_test
before_script:
- psql -c 'create database unleash_test;' -U postgres
script:
- npm install
- npm run test:coverage
after_success:
- npm run test:coverage-report
notifications:
  slack:
    secure: MroremSKwtQkwPbrXjgs9hIqKTCDKk7bAIXXzjcS6wXC9uRaFgwFaW8oO3vBxtWa4BL44EQBLE/rboWgqFER62+XgXNgEqGZqrcJHJvby4r+dUNMPI64OZvWdIiydIYxLo8C1C4x5PqBup0xuLq8h/SBnNvA2NLgkjuvzOi+v/Q=
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:`
use lerna for multipackaging 2016-06-18 09:19:57 +02:00			`- "6"`
			`env:`
			`- DATABASE_URL=postgres://postgres@localhost:5432/unleash_test TEST_DATABASE_URL=postgres://postgres@localhost:5432/unleash_test`
Bump mocha timeout on Travis 2014-11-12 15:15:23 +01:00			`before_script:`
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`
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`
fix coverals in travis 2016-11-10 21:38:19 +01:00			`- npm run test:coverage`
send coverage after success 2016-11-13 15:43:07 +01:00			`after_success:`
correct order 2016-11-10 21:41:22 +01:00			`- npm run test:coverage-report`
Add HipChat notifications 2014-09-30 19:43:15 +02:00			`notifications:`
Add Slack integration 2015-04-08 13:21:40 +02:00			`slack:`
			`secure: MroremSKwtQkwPbrXjgs9hIqKTCDKk7bAIXXzjcS6wXC9uRaFgwFaW8oO3vBxtWa4BL44EQBLE/rboWgqFER62+XgXNgEqGZqrcJHJvby4r+dUNMPI64OZvWdIiydIYxLo8C1C4x5PqBup0xuLq8h/SBnNvA2NLgkjuvzOi+v/Q=`
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"`