kotovalexarian-likes-github/heartcombo--devise
1
0
Fork 0
mirror of https://github.com/heartcombo/devise.git synced 2022-11-09 12:18:31 -05:00
Code Releases Activity
heartcombo--devise/.travis.yml

69 lines
1.5 KiB
YAML
Raw Normal View History

Update Travis CI configuration: * `DEVISE_ORM=mongoid` is part of the build matrix, except for 1.8.7 and REE rubies; * `language` key added (Thanks to travis-lint).
2012-11-12 06:12:17 -05:00
language: ruby
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
lets have travis test against many rubies
2011-04-04 14:29:46 -04:00
rvm:
Test against latest ruby versions
2017-03-02 06:11:08 -05:00
- 2.1.10
CI against Ruby 2.2.8, 2.3.5, and 2.4.2
2017-09-16 10:40:57 -04:00
- 2.2.8
- 2.3.5
- 2.4.2
Run tests on ruby 2.5.0
2017-12-29 12:08:49 -05:00
- 2.5.0
Update .travis.yml
2016-05-06 16:05:03 -04:00
- ruby-head
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
Let Devise play with both Rails 3.2 and Rails 4 for now
2013-05-03 21:56:46 -04:00
gemfile:
Reorder travis builds to prioritize newer ruby and rails versions
2016-02-10 14:20:36 -05:00
- Gemfile
Test on Rails 5.2.0.rc1 (#4711)
2018-02-22 08:05:19 -05:00
- gemfiles/Gemfile.rails-5.2-rc1
Test with Rails 5.0
2017-05-11 22:00:04 -04:00
- gemfiles/Gemfile.rails-5.0-stable
Test against Ruby 2.2 on Travis. * Add 4.2 stable to matrix. * Exclude test against Ruby 2.2 for Rails 3.2.
2014-12-27 03:05:43 -05:00
- gemfiles/Gemfile.rails-4.2-stable
Update Gemfile list on Travis.
2014-08-20 17:44:50 -04:00
- gemfiles/Gemfile.rails-4.1-stable
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
Test against Ruby 2.2 on Travis. * Add 4.2 stable to matrix. * Exclude test against Ruby 2.2 for Rails 3.2.
2014-12-27 03:05:43 -05:00
matrix:
Test against the beta Rails release.
2015-12-20 19:56:13 -05:00
exclude:
Skip running tests on Ruby 2.4 / head and Rails 4.1
2017-03-02 07:59:05 -05:00
- rvm: 2.1.10
Update `.travis.yml`.
2016-07-01 13:22:38 -04:00
gemfile: Gemfile
Test on Rails 5.2.0.rc1 (#4711)
2018-02-22 08:05:19 -05:00
- rvm: 2.1.10
gemfile: gemfiles/Gemfile.rails-5.2-rc1
Don't run ruby `2.5.0` with rails `4.1` https://github.com/rails/rails/issues/25125
2017-12-29 13:42:58 -05:00
- rvm: 2.5.0
gemfile: gemfiles/Gemfile.rails-4.1-stable
CI against Ruby 2.2.8, 2.3.5, and 2.4.2
2017-09-16 10:40:57 -04:00
- rvm: 2.4.2
Skip running tests on Ruby 2.4 / head and Rails 4.1
2017-03-02 07:59:05 -05:00
gemfile: gemfiles/Gemfile.rails-4.1-stable
- rvm: ruby-head
gemfile: gemfiles/Gemfile.rails-4.1-stable
Allow Rails 5.1
2017-02-26 12:58:38 -05:00
- rvm: 2.1.10
Test with Rails 5.0
2017-05-11 22:00:04 -04:00
gemfile: gemfiles/Gemfile.rails-5.0-stable
- rvm: 2.1.10
gemfile: Gemfile
Test against the beta Rails release.
2015-12-20 19:56:13 -05:00
- env: DEVISE_ORM=mongoid
Update `.travis.yml`.
2016-07-01 13:22:38 -04:00
gemfile: Gemfile
Allow Rails 5.1
2017-02-26 12:58:38 -05:00
- env: DEVISE_ORM=mongoid
Test with Rails 5.0
2017-05-11 22:00:04 -04:00
gemfile: gemfiles/Gemfile.rails-5.0-stable
Test on Rails 5.2.0.rc1 (#4711)
2018-02-22 08:05:19 -05:00
- env: DEVISE_ORM=mongoid
gemfile: gemfiles/Gemfile.rails-5.2-rc1
Update .travis.yml
2016-05-06 16:05:03 -04:00
allow_failures:
- rvm: ruby-head
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
services:
- mongodb
sudo: false
use built in travis caching make sure bundle update is run so that the latest gems are used
2014-11-19 17:08:07 -05:00
cache: bundler
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
env:
matrix:
- DEVISE_ORM=active_record
Reorder travis builds to prioritize newer ruby and rails versions
2016-02-10 14:20:36 -05:00
- DEVISE_ORM=mongoid
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
Run `gem update --system` before install on CI There's an issue with the combination of Bundler `1.16.1` and rubygems `2.7.3`. This command will install rubygems `2.7.4` in order to fix it. https://github.com/travis-ci/travis-ci/issues/8978
2017-12-29 13:11:04 -05:00
before_install:
- "rm ${BUNDLE_GEMFILE}.lock"
- gem update --system
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
use built in travis caching make sure bundle update is run so that the latest gems are used
2014-11-19 17:08:07 -05:00
before_script: "bundle update"
Add a `bin/test` executable to use Rails 5 Minitest report.
2016-03-09 09:16:21 -05:00
script: "bin/test"
Use the new build env on Travis - use the new build env on Travis (sudo: false) (docs coming soon) faster vms, more cpu, more ram, faster vm boot time - remove the custom caching for now as the new setup has a far better network - add rails-head to the gemfile list as it wasn't there caching is generally not recommended for libs like Devise as you want to test against the latest gem versions. Caching will use the min requirements available on the system instead of retrieving the latest. On that note, it is also recommended to remove the Gemfile.lock from the repo. For now I have just 'rm'd it before 'bundle install'
2014-11-19 13:49:55 -05:00
sets travis to report to maintainers
2011-09-08 07:31:34 -04:00
notifications:
Notify on campfire
2013-01-09 07:11:24 -05:00
email: false
Update Travis CI notification settings.
2015-11-01 16:54:58 -05:00
slack:
Do not send Travis notifications of Pull Requests.
2015-12-15 12:26:08 -05:00
on_pull_requests: false
Notify on campfire
2013-01-09 07:11:24 -05:00
on_success: change
on_failure: always
Update Travis CI notification settings.
2015-11-01 16:54:58 -05:00
secure: Q3M+kmude3FjisibEeeGe0wSMXgvwLH+vL7Zrx9//q4QtkfnrQ/BBMvY9KXxPEsNF+eys4YopYjTkJ8uRmeboUATW/oQ4Jrv3+u3zkIHK2sFn/Q2cQWpK5w+CbgEnHPjKYnUu34b09njXTgDlr/mqtbPqrKeZ1dLlpKXCB/q4GY=
Copy permalink