paper-trail-gem--paper_trail/.travis.yml

language: ruby
cache: bundler

# For ruby, we test the highest and lowest minor versions only.
rvm:
  - 2.4
  - 2.7

env:
  global:
    - TRAVIS=true
  matrix:
    - DB=mysql
    - DB=postgres
    - DB=sqlite

# Travis recommend we use the VM infrastructure (`sudo: required`)
sudo: required

before_install:
  - gem update bundler

gemfile:
  - gemfiles/ar_5.2.gemfile
  - gemfiles/ar_6.0.gemfile
matrix:
  exclude:
    # rails 6 requires ruby >= 2.5.0
    - rvm: 2.4
      gemfile: gemfiles/ar_6.0.gemfile
  fast_finish: true
services:
  - mysql
  - postgresql
Adding language declaration to .travis.yml 2012-11-27 20:59:21 +00:00			`language: ruby`
Update CI and linter configuration - ruby 2.3.1 (was 2.3.0) - Update AR5 gemfile now that rails 5 is out - Enable travis bundler cache. Hopefully this will speed up travis a bit. https://docs.travis-ci.com/user/caching/ - set TargetRubyVersion: 1.9 2016-08-09 04:09:15 +00:00			`cache: bundler`
Test 2.3 and 2.5, but not 2.4 2018-02-18 22:14:19 +00:00
Prepare for v11 (#1235) * Drop support for ruby 2.3 * Docs: appraisal * Drop support for rails <= 5.1 * Upgrade rubocop to 0.80 * Remove defunct code for EoL rails versions * Rails 5+ style controller test params keyword * Squash me Co-Authored-By: Todd Lynam <TLynam@gmail.com> Co-authored-by: Todd Lynam <TLynam@gmail.com> 2020-03-03 02:58:33 +00:00			`# For ruby, we test the highest and lowest minor versions only.`
Add Travis CI configuration. 2011-07-25 20:08:44 +00:00			`rvm:`
Prepare for v11 (#1235) * Drop support for ruby 2.3 * Docs: appraisal * Drop support for rails <= 5.1 * Upgrade rubocop to 0.80 * Remove defunct code for EoL rails versions * Rails 5+ style controller test params keyword * Squash me Co-Authored-By: Todd Lynam <TLynam@gmail.com> Co-authored-by: Todd Lynam <TLynam@gmail.com> 2020-03-03 02:58:33 +00:00			`- 2.4`
Test with Ruby 2.7 2020-01-02 14:43:51 +00:00			`- 2.7`
Test 2.3 and 2.5, but not 2.4 2018-02-18 22:14:19 +00:00
Adding Full Support to Test Against Multiple DB engines. Accomplished by swapping out database.yml files for the dummy rails instance with en engine specific one. 2014-03-14 20:11:10 +00:00			`env:`
Add global ENV flag on runs in Travis to make it detectable 2015-03-25 23:41:10 +00:00			`global:`
			`- TRAVIS=true`
			`matrix:`
			`- DB=mysql`
			`- DB=postgres`
			`- DB=sqlite`
Use TravisCI's VM infrastructure temporarily 2018-09-17 18:59:42 +00:00
CI: Drop mention of removed directive sudo: false This is an attempt to simplify the comment 2020-07-15 09:07:57 +00:00			# Travis recommend we use the VM infrastructure (`sudo: required`)
Use TravisCI's VM infrastructure temporarily 2018-09-17 18:59:42 +00:00			`sudo: required`

Support rails 6.0.0 (#1172) * Change update_attributes to update In Rails 6.0 update_attributes/update_attributes! is considered deprecated. Method update/update! is the replacement. * CI: Don't use Bundler 1.16.1 - Bundler 1.16.1 has bug where dependencies can't be resolved properly when a gem is a release candidate or an alpha version. The underlying bundler issue can be found here https://github.com/bundler/bundler/issues/6449 * Disable eager_load in test env: - In Rails 6.0, rails/rails@3b95478 made a change to eagerly define attribute methods of a Model when `eager_load` is enabled. This breaks our test suite because of the way we run migration. The TL;DR is that doing `People.attribute_names` will return an empty array instead of `[:id, time_zone, ...]`. You can find a failing build here https://travis-ci.org/paper-trail-gem/paper_trail/jobs/463369634 Basically what happens is: 1) The dummy app boot, attribute methods of each model are defined but since migration didn't run yet, the tables aren't even created resulting in a empty attribute set. 2) Migration runs, but it's already too late. In this commit I disabled eager_loading in test, AFAIT there isn't much benefit in eager_loading the dummy app anyway. Also renaming the `user.rb` file to `postgres_user.rb` in order for rails autoloading to work correctly. 2018-12-04 21:10:35 +00:00			`before_install:`
			`- gem update bundler`

Adjusting Travis CI config to cover ActiveRecord 3 and 4 and allow failures when appropriate, tweaked 3.0.gemfile so it can handle ruby18 and jruby 2013-08-01 18:59:58 +00:00			`gemfile:`
Add support to Rails 5.2 2018-03-20 15:25:13 +00:00			`- gemfiles/ar_5.2.gemfile`
Support rails 6.0.0 (#1172) * Change update_attributes to update In Rails 6.0 update_attributes/update_attributes! is considered deprecated. Method update/update! is the replacement. * CI: Don't use Bundler 1.16.1 - Bundler 1.16.1 has bug where dependencies can't be resolved properly when a gem is a release candidate or an alpha version. The underlying bundler issue can be found here https://github.com/bundler/bundler/issues/6449 * Disable eager_load in test env: - In Rails 6.0, rails/rails@3b95478 made a change to eagerly define attribute methods of a Model when `eager_load` is enabled. This breaks our test suite because of the way we run migration. The TL;DR is that doing `People.attribute_names` will return an empty array instead of `[:id, time_zone, ...]`. You can find a failing build here https://travis-ci.org/paper-trail-gem/paper_trail/jobs/463369634 Basically what happens is: 1) The dummy app boot, attribute methods of each model are defined but since migration didn't run yet, the tables aren't even created resulting in a empty attribute set. 2) Migration runs, but it's already too late. In this commit I disabled eager_loading in test, AFAIT there isn't much benefit in eager_loading the dummy app anyway. Also renaming the `user.rb` file to `postgres_user.rb` in order for rails autoloading to work correctly. 2018-12-04 21:10:35 +00:00			`- gemfiles/ar_6.0.gemfile`
Adding Ruby2 back onto .travis.yml but with failures allowed, as per req #210 2013-03-08 16:12:23 +00:00			`matrix:`
Support rails 6.0.0 (#1172) * Change update_attributes to update In Rails 6.0 update_attributes/update_attributes! is considered deprecated. Method update/update! is the replacement. * CI: Don't use Bundler 1.16.1 - Bundler 1.16.1 has bug where dependencies can't be resolved properly when a gem is a release candidate or an alpha version. The underlying bundler issue can be found here https://github.com/bundler/bundler/issues/6449 * Disable eager_load in test env: - In Rails 6.0, rails/rails@3b95478 made a change to eagerly define attribute methods of a Model when `eager_load` is enabled. This breaks our test suite because of the way we run migration. The TL;DR is that doing `People.attribute_names` will return an empty array instead of `[:id, time_zone, ...]`. You can find a failing build here https://travis-ci.org/paper-trail-gem/paper_trail/jobs/463369634 Basically what happens is: 1) The dummy app boot, attribute methods of each model are defined but since migration didn't run yet, the tables aren't even created resulting in a empty attribute set. 2) Migration runs, but it's already too late. In this commit I disabled eager_loading in test, AFAIT there isn't much benefit in eager_loading the dummy app anyway. Also renaming the `user.rb` file to `postgres_user.rb` in order for rails autoloading to work correctly. 2018-12-04 21:10:35 +00:00			`exclude:`
Support ruby 2.6.0 2019-01-02 00:14:47 +00:00			`# rails 6 requires ruby >= 2.5.0`
Prepare for v11 (#1235) * Drop support for ruby 2.3 * Docs: appraisal * Drop support for rails <= 5.1 * Upgrade rubocop to 0.80 * Remove defunct code for EoL rails versions * Rails 5+ style controller test params keyword * Squash me Co-Authored-By: Todd Lynam <TLynam@gmail.com> Co-authored-by: Todd Lynam <TLynam@gmail.com> 2020-03-03 02:58:33 +00:00			`- rvm: 2.4`
Support rails 6.0.0 (#1172) * Change update_attributes to update In Rails 6.0 update_attributes/update_attributes! is considered deprecated. Method update/update! is the replacement. * CI: Don't use Bundler 1.16.1 - Bundler 1.16.1 has bug where dependencies can't be resolved properly when a gem is a release candidate or an alpha version. The underlying bundler issue can be found here https://github.com/bundler/bundler/issues/6449 * Disable eager_load in test env: - In Rails 6.0, rails/rails@3b95478 made a change to eagerly define attribute methods of a Model when `eager_load` is enabled. This breaks our test suite because of the way we run migration. The TL;DR is that doing `People.attribute_names` will return an empty array instead of `[:id, time_zone, ...]`. You can find a failing build here https://travis-ci.org/paper-trail-gem/paper_trail/jobs/463369634 Basically what happens is: 1) The dummy app boot, attribute methods of each model are defined but since migration didn't run yet, the tables aren't even created resulting in a empty attribute set. 2) Migration runs, but it's already too late. In this commit I disabled eager_loading in test, AFAIT there isn't much benefit in eager_loading the dummy app anyway. Also renaming the `user.rb` file to `postgres_user.rb` in order for rails autoloading to work correctly. 2018-12-04 21:10:35 +00:00			`gemfile: gemfiles/ar_6.0.gemfile`
Add 'generator_spec' gem to rails3 Gemfile for Travis; use :fast_finish option on Travis 2014-03-07 21:26:41 +00:00			`fast_finish: true`
Try testing against mysql again 2019-08-01 17:43:37 +00:00			`services:`
			`- mysql`
			`- postgresql`