thoughtbot--shoulda-matchers/.travis.yml

language: ruby
sudo: false
cache: bundler
script: "bundle exec rake"
# Source: <https://docs.travis-ci.com/user/languages/ruby/#bundler-20>
before_install:
  - gem uninstall -v '>= 2' -i $(rvm gemdir)@global -ax bundler || true
  - gem install bundler -v '< 2'
install: "bundle install --jobs=3 --retry=3"

env:
  - DATABASE_ADAPTER=sqlite3
  - DATABASE_ADAPTER=postgresql

rvm:
  - 2.5.1
  - 2.4.4
  - 2.3.7

gemfile:
  - gemfiles/4.2.gemfile
  - gemfiles/5.0.gemfile
  - gemfiles/5.1.gemfile
  - gemfiles/5.2.gemfile
Enable caching 2014-10-21 02:41:01 -04:00			`language: ruby`
Exclude site and gh-pages branches from Travis 2015-01-23 16:11:47 -05:00			`sudo: false`
Cache Bundler on Travis With Container based CI, public projects can cache the results of `bundle install` 2015-02-20 13:14:56 -05:00			`cache: bundler`
Exclude site and gh-pages branches from Travis 2015-01-23 16:11:47 -05:00			`script: "bundle exec rake"`
Lock Bundler to 1.x Bundler 2.0 was released recently, but none of our lockfiles are associated with this version — they all refer to Bundler 1.x. Unfortunately, Travis is now attempting to use Bundler 2.0 by default, so we have to ensure that it is using the correct version as well. 2019-01-28 21:15:28 -05:00			`# Source: <https://docs.travis-ci.com/user/languages/ruby/#bundler-20>`
			`before_install:`
			`- gem uninstall -v '>= 2' -i $(rvm gemdir)@global -ax bundler \|\| true`
			`- gem install bundler -v '< 2'`
Override the way gems are installed on Travis It seems that Travis has made a change where instead of installing gems globally they are installed to `vendor/gems`. This happens because all of our Appraisal Gemfiles have associated lockfiles that are present in the repo and Travis picks up on this and choose to run `bundle with `--deployment`. This breaks our acceptance tests as they assume that gems are installed globally. To get around this we need to define our own `install` command. 2017-11-09 01:54:03 -05:00			`install: "bundle install --jobs=3 --retry=3"`
Exclude site and gh-pages branches from Travis 2015-01-23 16:11:47 -05:00
Add support for Postgres When running tests, you can now switch between running them against a SQLite or PostgreSQL database. This is accomplished by modifying the unit and acceptance tests so that when they generate and load the test Rails application, database.yml is replaced with content that will configure the database appropriately. 2015-02-08 16:38:55 -05:00			`env:`
			`- DATABASE_ADAPTER=sqlite3`
			`- DATABASE_ADAPTER=postgresql`

Add travis build 2011-09-12 06:48:27 -04:00			`rvm:`
Add TravisCI Ruby 2.5.1 builds 2018-09-03 21:05:11 -04:00			`- 2.5.1`
Update supported Ruby and Rails versions 2018-09-13 01:58:33 -04:00			`- 2.4.4`
			`- 2.3.7`
Use the new beta build env on Travis faster vm boot times more cpus more ram better network docs coming soon 2014-11-18 05:04:51 -05:00
Add travis build 2011-09-12 06:48:27 -04:00			`gemfile:`
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now. 2014-10-22 00:35:12 -04:00			`- gemfiles/4.2.gemfile`
Add Rails 5 appraisal 2016-09-03 23:31:40 -04:00			`- gemfiles/5.0.gemfile`
Run tests under Rails 5.1 on Travis 2017-09-17 19:10:00 -04:00			`- gemfiles/5.1.gemfile`
Create Appraisal and TravisCI config for Rails 5.2 2018-09-03 20:57:20 -04:00			`- gemfiles/5.2.gemfile`