heartcombo--devise/.travis.yml

language: ruby

rvm:
  - 2.1.10
  - 2.2.6
  - 2.3.3
  - 2.4.0
  - ruby-head

gemfile:
  - Gemfile
  - gemfiles/Gemfile.rails-5.1-stable
  - gemfiles/Gemfile.rails-4.2-stable
  - gemfiles/Gemfile.rails-4.1-stable

matrix:
  exclude:
    - rvm: 2.1.10
      gemfile: Gemfile
    - rvm: 2.4.0
      gemfile: gemfiles/Gemfile.rails-4.1-stable
    - rvm: ruby-head
      gemfile: gemfiles/Gemfile.rails-4.1-stable
    - rvm: 2.1.10
      gemfile: gemfiles/Gemfile.rails-5.1-stable
    - env: DEVISE_ORM=mongoid
      gemfile: Gemfile
    - env: DEVISE_ORM=mongoid
      gemfile: gemfiles/Gemfile.rails-5.1-stable
  allow_failures:
    - rvm: ruby-head
services:
  - mongodb

sudo: false

cache: bundler

env:
  matrix:
    - DEVISE_ORM=active_record
    - DEVISE_ORM=mongoid

before_install: "rm ${BUNDLE_GEMFILE}.lock"

before_script: "bundle update"

script: "bin/test"

notifications:
  email: false
  slack:
    on_pull_requests: false
    on_success: change
    on_failure: always
    secure: Q3M+kmude3FjisibEeeGe0wSMXgvwLH+vL7Zrx9//q4QtkfnrQ/BBMvY9KXxPEsNF+eys4YopYjTkJ8uRmeboUATW/oQ4Jrv3+u3zkIHK2sFn/Q2cQWpK5w+CbgEnHPjKYnUu34b09njXTgDlr/mqtbPqrKeZ1dLlpKXCB/q4GY=
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 11:12:17 +00: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 18:49:55 +00:00
lets have travis test against many rubies 2011-04-04 18:29:46 +00:00			`rvm:`
Test against latest ruby versions 2017-03-02 11:11:08 +00:00			`- 2.1.10`
			`- 2.2.6`
			`- 2.3.3`
			`- 2.4.0`
Update .travis.yml 2016-05-06 20:05:03 +00: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 18:49:55 +00:00
Let Devise play with both Rails 3.2 and Rails 4 for now 2013-05-04 01:56:46 +00:00			`gemfile:`
Reorder travis builds to prioritize newer ruby and rails versions 2016-02-10 19:20:36 +00:00			`- Gemfile`
Allow Rails 5.1 2017-02-26 17:58:38 +00:00			`- gemfiles/Gemfile.rails-5.1-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 08:05:43 +00:00			`- gemfiles/Gemfile.rails-4.2-stable`
Update Gemfile list on Travis. 2014-08-20 21:44:50 +00: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 18:49:55 +00: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 08:05:43 +00:00			`matrix:`
Test against the beta Rails release. 2015-12-21 00:56:13 +00:00			`exclude:`
Skip running tests on Ruby 2.4 / head and Rails 4.1 2017-03-02 12:59:05 +00:00			`- rvm: 2.1.10`
Update `.travis.yml`. 2016-07-01 17:22:38 +00:00			`gemfile: Gemfile`
Skip running tests on Ruby 2.4 / head and Rails 4.1 2017-03-02 12:59:05 +00:00			`- rvm: 2.4.0`
			`gemfile: gemfiles/Gemfile.rails-4.1-stable`
			`- rvm: ruby-head`
			`gemfile: gemfiles/Gemfile.rails-4.1-stable`
Allow Rails 5.1 2017-02-26 17:58:38 +00:00			`- rvm: 2.1.10`
			`gemfile: gemfiles/Gemfile.rails-5.1-stable`
Test against the beta Rails release. 2015-12-21 00:56:13 +00:00			`- env: DEVISE_ORM=mongoid`
Update `.travis.yml`. 2016-07-01 17:22:38 +00:00			`gemfile: Gemfile`
Allow Rails 5.1 2017-02-26 17:58:38 +00:00			`- env: DEVISE_ORM=mongoid`
			`gemfile: gemfiles/Gemfile.rails-5.1-stable`
Update .travis.yml 2016-05-06 20:05:03 +00: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 18:49:55 +00: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 22:08:07 +00: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 18:49:55 +00:00			`env:`
			`matrix:`
			`- DEVISE_ORM=active_record`
Reorder travis builds to prioritize newer ruby and rails versions 2016-02-10 19:20:36 +00: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 18:49:55 +00:00
remove the relevant Gemfile.lock 2014-11-19 19:54:31 +00:00			`before_install: "rm ${BUNDLE_GEMFILE}.lock"`
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 18:49:55 +00:00
use built in travis caching make sure bundle update is run so that the latest gems are used 2014-11-19 22:08:07 +00:00			`before_script: "bundle update"`

Add a `bin/test` executable to use Rails 5 Minitest report. 2016-03-09 14:16:21 +00: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 18:49:55 +00:00
sets travis to report to maintainers 2011-09-08 11:31:34 +00:00			`notifications:`
Notify on campfire 2013-01-09 12:11:24 +00:00			`email: false`
Update Travis CI notification settings. 2015-11-01 21:54:58 +00:00			`slack:`
Do not send Travis notifications of Pull Requests. 2015-12-15 17:26:08 +00:00			`on_pull_requests: false`
Notify on campfire 2013-01-09 12:11:24 +00:00			`on_success: change`
			`on_failure: always`
Update Travis CI notification settings. 2015-11-01 21:54:58 +00:00			`secure: Q3M+kmude3FjisibEeeGe0wSMXgvwLH+vL7Zrx9//q4QtkfnrQ/BBMvY9KXxPEsNF+eys4YopYjTkJ8uRmeboUATW/oQ4Jrv3+u3zkIHK2sFn/Q2cQWpK5w+CbgEnHPjKYnUu34b09njXTgDlr/mqtbPqrKeZ1dLlpKXCB/q4GY=`