kotovalexarian-likes-github
/
heartcombo--devise
mirror of https://github.com/heartcombo/devise.git
1
0
Fork 0
Code Releases Activity
heartcombo--devise/.travis.yml

43 lines
807 B
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 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:
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
- 2.1
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
- 2.2
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:
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
Let Devise play with both Rails 3.2 and Rails 4 for now
2013-05-04 01:56:46 +00:00
- Gemfile
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:
Rails 5 compatability. Remove rails < 4.1 and Ruby < 2.1
2015-08-18 23:42:56 +00:00
include:
- rvm: 2.2.2
gemfile: gemfiles/Gemfile.rails-5.0-alpha
allow_failures:
- rvm: 2.2.2
gemfile: gemfiles/Gemfile.rails-5.0-alpha
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=mongoid
- DEVISE_ORM=active_record
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"
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
script: "bundle exec rake test"
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:
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=