dendrite/.travis.yml

language: go
go:
 - 1.8.x
 - 1.9.x

env:
- TEST_SUITE="lint"
- TEST_SUITE="unit-test"
- TEST_SUITE="integ-test"

sudo: false

# Use trusty for postgres 9.5 support
dist: trusty

addons:
  postgresql: "9.5"

services:
  - postgresql

install:
 - go get github.com/constabulary/gb/...

script:
 - ./scripts/travis-test.sh
Add .travis.yaml 2017-02-10 04:54:07 -06:00			`language: go`
			`go:`
Use latest versions of go (#369) 2017-12-12 04:25:24 -06:00			`- 1.8.x`
			`- 1.9.x`
Split travis into multiple jobs (#322) The motivation for this is to make it easier to see whether a travis failure is due to linting, unit tests or integration test failures, without having to look in the logs. It also means that each job is independent, so if e.g. the linting fails then the unit tests will still be run. 2017-11-14 08:58:27 -06:00
			`env:`
			`- TEST_SUITE="lint"`
			`- TEST_SUITE="unit-test"`
			`- TEST_SUITE="integ-test"`
Add integration tests for roomserver to travis (#21) * Add integration tests for roomserver to travis * Try setting the dist trusty to see if that helps with postgres * Pretty print the test input JSON * Add comment as to why we are using trusty 2017-03-01 08:55:27 -06:00
			`sudo: false`

			`# Use trusty for postgres 9.5 support`
			`dist: trusty`

			`addons:`
			`postgresql: "9.5"`

			`services:`
			`- postgresql`

Add .travis.yaml 2017-02-10 04:54:07 -06:00			`install:`
			`- go get github.com/constabulary/gb/...`

Add coveralls.io? 2017-02-20 11:13:59 -06:00			`script:`
Untangle precommit and travis test scripts (#288) 2017-10-10 05:02:39 -05:00			`- ./scripts/travis-test.sh`
Add .travis.yaml 2017-02-10 04:54:07 -06:00