kotovalexarian-likes-github/paper-trail-gem--paper_trail
1
0
Fork 0
mirror of https://github.com/paper-trail-gem/paper_trail.git synced 2022-11-09 11:33:19 -05:00
Code Releases Activity
paper-trail-gem--paper_trail/.travis.yml

52 lines
1.2 KiB
YAML
Raw Normal View History

Adding language declaration to .travis.yml
2012-11-27 15:59:21 -05: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 00:09:15 -04:00
cache: bundler
Test 2.3 and 2.5, but not 2.4
2018-02-18 17:14:19 -05:00
# For ruby compatibility, we test the highest and lowest minor versions only.
# For example, if our gemspec says `required_ruby_version = ">= 2.3.0"`, and
# ruby 2.5.0 has just been released, then we test 2.3 and 2.5, but not 2.4.
Add Travis CI configuration.
2011-07-25 16:08:44 -04:00
rvm:
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 16:10:35 -05:00
- 2.3.8
- 2.4.5
- 2.5.3
Test 2.3 and 2.5, but not 2.4
2018-02-18 17:14:19 -05: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 16:11:10 -04:00
env:
Add global ENV flag on runs in Travis to make it detectable
2015-03-25 19:41:10 -04:00
global:
- TRAVIS=true
matrix:
- DB=mysql
- DB=postgres
- DB=sqlite
Use TravisCI's VM infrastructure temporarily
2018-09-17 14:59:42 -04:00
# We want to use `sudo: false` because the container infrastructure is supposed
# to be faster, but Travis is having issues with containers lately ..
#
# > No output has been received in the last 10m0s
#
# .. and they recommend we use the VM infrastructure (`sudo: required`) in
# the meantime.
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 16:10:35 -05: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 14:59:58 -04:00
gemfile:
Drop support for rails 3 In https://github.com/airblade/paper_trail/pull/895, Sean asked: > .. since it looks like the next version is planned to be 6.0.0, how would > you feel about dropping support for Rails 3 in that version? It has > reached end of life, meaning it no longer receives security patches. We > don't recommend that gem authors continue to support it. To which, I responded: > We could continue maintaining PT 5 if we had to, so I think it's > fine to drop support for rails 3 in PT 6. If Ben agrees, I'd be > happy to make that change. I'll just update the gemspec and drop > testing support, for starters. We can clean up the conditionals in > the code over time.
2016-11-30 12:03:22 -05:00
- gemfiles/ar_4.2.gemfile
Add AR 5.1 to CI matrix
2017-04-27 00:21:04 -04:00
- gemfiles/ar_5.1.gemfile
Add support to Rails 5.2
2018-03-20 11:25:13 -04: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 16:10:35 -05:00
- gemfiles/ar_6.0.gemfile
Adding Ruby2 back onto .travis.yml but with failures allowed, as per req #210
2013-03-08 11:12:23 -05: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 16:10:35 -05:00
exclude:
# rails 6 will not support ruby < 2.4.1
- rvm: 2.3.8
gemfile: gemfiles/ar_6.0.gemfile
# optimization: don't test intermediate rubies (see above)
- rvm: 2.4.5
gemfile: gemfiles/ar_4.2.gemfile
- rvm: 2.4.5
gemfile: gemfiles/ar_5.1.gemfile
- rvm: 2.4.5
gemfile: gemfiles/ar_5.2.gemfile
Add 'generator_spec' gem to rails3 Gemfile for Travis; use :fast_finish option on Travis
2014-03-07 16:26:41 -05:00
fast_finish: true
Bump Postgres version in CI
2015-04-09 15:34:58 -04:00
addons:
postgresql: "9.4"
Copy permalink