thoughtbot--factory_bot/.travis.yml

rvm:
  - 1.9.3
  - 2.0.0
  - 2.1.0
  - 2.2.2
  - 2.3.0
  - jruby-19mode
  - rbx-2
before_install:
  - gem update --system
  - gem update bundler
  - gem cleanup bundler
install: "bundle install"
script: "bundle exec rake"
gemfile:
  - gemfiles/3.2.gemfile
  - gemfiles/4.0.gemfile
  - gemfiles/4.1.gemfile
  - gemfiles/4.2.gemfile
  - gemfiles/5.0.gemfile
matrix:
  fast_finish: true
  allow_failures:
    - rvm: jruby-19mode
      gemfile: gemfiles/5.0.gemfile
    - rvm: 1.9.3
      gemfile: gemfiles/5.0.gemfile
    - rvm: 2.0.0
      gemfile: gemfiles/5.0.gemfile
    - rvm: 2.1.0
      gemfile: gemfiles/5.0.gemfile
    - rvm: rbx-2
      gemfile: gemfiles/5.0.gemfile
branches:
  only:
    - master

sudo: false
cache: bundler
Bring back travis and try their gemfile option 2011-07-29 18:19:30 -04:00			`rvm:`
Update travis.yml to run against latest versions of Ruby instead of specifying patchlevel 2012-01-07 22:33:25 -05:00			`- 1.9.3`
Add Ruby 2.0.0 to list of versions to test on Travis 2013-11-02 13:00:19 -04:00			`- 2.0.0`
Add Ruby 2.1.0 to .travis.yml 2014-01-05 04:27:34 -05:00			`- 2.1.0`
Support Ruby 2.2 * Remove Rails 3.1 support * Bump Rails 3.2 to stable 2015-04-14 22:35:01 -04:00			`- 2.2.2`
Run against Ruby 2.3 on Travis 2016-03-30 16:50:36 -04:00			`- 2.3.0`
Adding JRuby support to FactoryGirl JRuby are affected by inconsistent behavior of overriding #respond_to? that is causing an unconditional call to #respond_to_missing. Current change does not affect MRI users in any way, JRuby-specific things are wrapped into the RUBY_PLATFORM check. Adding docs, modifying gemspec and travis.yml to make factory_girl to pass on Travis. Wire up tests 2012-07-06 05:27:40 -04:00			`- jruby-19mode`
Add Rubinius to Build Matrix Fix unintended removal of new line here 2015-02-20 18:45:32 -05:00			`- rbx-2`
Update rubygems on travis-ci.org before running dependency installation REE will fail to install Rails 3.2 gems w/o rubygems update. 2012-01-29 10:56:37 -05:00			`before_install:`
			`- gem update --system`
Update bundler before in Travis CI builds Builds are broken because the `bundler` version that Travis CI automatically uses at this time (`1.7.6`) is coming across an error that was fixed in a later version/release. Having an outdated version of `bundler` in the Travis CI builds is an ongoing issue and this is currently the easiest work-around. See: * https://github.com/bundler/bundler/issues/3558 * https://github.com/travis-ci/travis-ci/issues/3531 [fixes #846] 2015-12-07 19:26:04 -05:00			`- gem update bundler`
Run against Ruby 2.3 on Travis 2016-03-30 16:50:36 -04:00			`- gem cleanup bundler`
Force 'bundle install' when installing 2013-10-08 13:03:30 -04:00			`install: "bundle install"`
Improve default rake task by removing appraisal 2016-02-05 10:09:50 -05:00			`script: "bundle exec rake"`
Bring back travis and try their gemfile option 2011-07-29 18:19:30 -04:00			`gemfile:`
Travis runs the 3.2 Gemfile 2012-01-13 14:23:33 -05:00			`- gemfiles/3.2.gemfile`
Ensure FG is tested against Rails 4 on Travis 2013-11-02 11:04:20 -04:00			`- gemfiles/4.0.gemfile`
Test against Rails 4.1 2014-05-30 12:34:10 -04:00			`- gemfiles/4.1.gemfile`
Test against Rails 4.2 * Update callbacks spec so column types reflect assignment Rails 4.2 introduces type coercion on attribute assignment instead of it occurring after persisting the record. 2015-04-15 21:50:33 -04:00			`- gemfiles/4.2.gemfile`
Appraise against Rails 5.0.0.beta Why? With Rails' upcoming release, test against the latest beta of Rails 5. 2016-02-05 15:04:57 -05:00			`- gemfiles/5.0.gemfile`
			`matrix:`
			`fast_finish: true`
			`allow_failures:`
			`- rvm: jruby-19mode`
			`gemfile: gemfiles/5.0.gemfile`
			`- rvm: 1.9.3`
			`gemfile: gemfiles/5.0.gemfile`
			`- rvm: 2.0.0`
			`gemfile: gemfiles/5.0.gemfile`
			`- rvm: 2.1.0`
			`gemfile: gemfiles/5.0.gemfile`
			`- rvm: rbx-2`
			`gemfile: gemfiles/5.0.gemfile`
Only build master in travis 2011-09-12 15:58:03 -04:00			`branches:`
			`only:`
			`- master`
Cache Bundler on Travis http://docs.travis-ci.com/user/workers/container-based-infrastructure/ With Container based CI, public projects can cache the results of bundle install 2015-02-20 13:18:00 -05:00
			`sudo: false`
			`cache: bundler`