1
0
Fork 0
mirror of https://github.com/thoughtbot/factory_bot_rails.git synced 2022-11-09 11:49:18 -05:00
Commit graph

33 commits

Author SHA1 Message Date
Yasuo Honda
dfeb7a66fb Address Bundler could not find compatible versions for gem "bundler":
https://travis-ci.org/thoughtbot/factory_bot_rails/jobs/567563177#L333-L355

```ruby
Bundler could not find compatible versions for gem "bundler":
  In rails4.2.gemfile:
    appraisal was resolved to 2.2.0, which depends on
      bundler

    rails (~> 4.2.11) was resolved to 4.2.11.1, which depends on
      bundler (>= 1.3.0, < 2.0)

  Current Bundler version:
    bundler (2.0.2)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 1.3.0, < 2.0)', which is required by gem 'rails
(~> 4.2.11)', in any of the sources.

Bundler could not find compatible versions for gem "cucumber":
  In rails4.2.gemfile:
    cucumber (= 1.3.19)

    aruba was resolved to 0.14.11, which depends on
      cucumber (>= 1.3.19)
The command "bundle install --retry 3 --jobs 8" failed and exited with 6 during .
```

because the latest version of Bundler is 2.0.2 since June 13, 2019

https://rubygems.org/gems/bundler/versions/2.0.2
2019-08-18 21:08:12 -04:00
Daniel Colson
8c09393993 Test against rails 6.0 2019-04-04 08:54:38 -04:00
Daniel Colson
ab8ed30424 Use an older version of bundler
Rails 4.2 requires bundler < 2.0, but on travis are getting 2.0.1
There is probably a better way to do this so we don't have to update
this every time travis starts using a new version, but I am going to
merge this for now to unblock the release of 5.0.0.rc1
2019-01-06 00:39:16 -05:00
Daniel Colson
139c87cd2e
Run CI on Ruby 2.6 2019-01-05 22:30:30 -05:00
Daniel Colson
75d1f68d12 Stop testing old Ruby and Rails versions
Ruby 2.1 and 2.2 are no longer maintained, and Rails 3.2 and 4.2 are no
longer maintained, so I don't want to go out of our way to continue
supporting them in FactoryBot 5+. Hooray for faster test runs!
2018-09-08 01:48:42 +00:00
Daniel Colson
3f2a8249f0 Don't run Rails 4.1 with Ruby head on travis
Rails 4.1 does not work with Ruby 2.4 or higher, so no need to run a
combination we know will fail.
2018-07-17 21:49:55 -04:00
Daniel Colson
c9fc696325
Test against Rails 5.1 and 5.2 (#278)
- Add Rails 5.1 and 5.2 to Appraisal
- Avoid running combinations we know are going to fail by moving to
"exclude" instead of "allow_failures"
- Use updated migration class for Rails 5.1+
2018-06-22 13:33:59 -04:00
naofumi-fujii
79b232434c Test with ruby-head on Travis 2018-06-14 22:27:36 -04:00
Oli Peate
5afdd7f900 Don't run Rails 4.1 appraisal with Ruby 2.4/2.5 on CI 2018-06-01 17:22:11 +01:00
Oli Peate
ae37b354d7 Drop jruby & add modern Rubies to Travis config 2018-05-25 16:52:21 +01:00
Joshua Clayton
1a694997c0 Appraise against Rails 5.0.0.beta3 2016-04-07 17:53:06 -04:00
Joshua Clayton
9e0b178c6f Correctly configure Aruba command timeout
This removes the misconfiguration of Aruba timeout by instance variable
2016-04-07 17:52:00 -04:00
Joshua Clayton
6b8ba60031 Test against Ruby 2.2.4 2016-04-05 11:55:08 -04:00
Joshua Clayton
50c1cb55bc Add Ruby 2.3.0 to list of versions to test on Travis 2016-04-04 09:06:29 -04:00
Joshua Clayton
b0dd2447c1 Don't run tests with JDK 2016-04-01 15:18:20 -04:00
Joshua Clayton
f83260e800 bundle install with jobs 2016-04-01 11:57:31 -04:00
Joshua Clayton
1d53c1659e Update and clean bundler prior to running the test suite 2016-04-01 11:12:38 -04:00
Joshua Clayton
8c16ae46e8 Bump versions of Ruby and Rails to test on Travis
* support latest Ruby 2.1
* support latest Ruby 2.2
* support latest Rails 4.2
* drop testing of Ruby 2.0
* drop testing of Rails 4.0
* fix JRuby support
2015-03-14 20:14:50 -04:00
Joshua Clayton
37b1f02b9f Explicitly define gemfiles for Travis
Closes #122
2014-07-25 16:11:58 -04:00
Dan Croak
39217eb028 Update Travis to run against latest Ruby, Rails
* Set up Appraisal before running `rake`.
* Add Ruby 2.1.2 to the testing matrix.
* Reduce the Travis matrix size.
2014-05-27 00:41:28 -07:00
Dan Croak
00cb2eabb1 Test against Rails 3.2, 4.0, 4.1
* Remove gemfiles from version control to match same testing style as
  Clearance and Suspenders.
* MiniTest does not need to be manually included as it is automatically
  included by Rails by default.
* Add spring for Rails 4.1.
* Disable Spring to get specs to pass on Rails 4.1.
* Add therubyrhino for JRuby.
* Remove old references to Rails 3.
* Fix JRuby test where output is "1 runs", not "1 tests".
* Remove Rails 3.0 reference to "turn".
2014-05-27 00:41:24 -07:00
Joshua Clayton
78d936650d Update version of Rubies tested by Travis 2013-11-03 22:46:30 -05:00
Joshua Clayton
aa40389c7b Remove Rails 3 from appraised versions of Rails 2013-11-03 22:46:03 -05:00
Matt Jankowski
5b099f6773 Allow Rails 3.1 to select the 'turn' gem it wants to use
Rails 3.1.x has code which checks which version of ruby is being run,
and based on the result, selects a version of turn.

For 1.9.3+, it selects "~> 0.8.3"; for everything else, it selects "0.8.2".

If we remove turn from the Appraisals, but have travis install both versions
that rails might potentially need, the in-generated-app Gemfile building should
work correctly.
2013-01-07 16:42:54 -05:00
Matt Jankowski
f68f1c234d Allow each Appraisal version gemfile to resolve the exact gem versions needed 2013-01-07 13:03:55 -05:00
Matt Jankowski
c97d2aeba1 Allow the rails 3.1 appraisal to select the exact version of turn it needs, dont install before hand 2013-01-04 15:37:36 -05:00
Matt Jankowski
ffca1ce373 Be more specific about which gems are required for which rails versions via Appraisals 2013-01-04 11:13:25 -05:00
Matt Jankowski
2f64464027 Make sure the gems that the rails apps are going to need are in place ahead of time 2012-12-21 11:08:23 -05:00
Matt Jankowski
89a257c951 Use minitest-rails only when we actually want to test it.
Some features test the factory_girl_rails integration with minitest-rails.

Other features just test normal integration with rails generators.

When minitest-rails is *always* in our gemfiles, minitest's generator
gets run during the features which generate new rails apps.

Because minitest doesnt support namespaced models, this fails.  But, also,
we don't actually want to run minitest during anything other than the specific
areas where we are testing that integration.

Thus, we need the gem present on the system, but not in the gemfiles during
any times other than when it's pulled in specifically by those features.
2012-12-13 12:02:21 -05:00
Matt Jankowski
0e417981e0 Regenerate gemfiles using newer Appraisal naming convention, point travis at correct files 2012-12-13 11:42:32 -05:00
Joshua Clayton
7d7828888c Bundle in an attempt to fix travis 2012-12-07 11:51:01 -05:00
Joshua Clayton
f2b5b79dd9 Install gems required by appraisal 2012-12-07 11:00:44 -05:00
Gabe Berke-Williams
6189e6028c Add travis.yml
Copied from factory_girl.
2012-11-30 11:55:26 -05:00