rails--rails/.travis.yml

script: 'ci/travis.rb'
before_install:
  - travis_retry gem install bundler
  - "rvm current | grep 'jruby' && export AR_JDBC=true || echo"
rvm:
  - 1.9.3
  - 2.0.0
  - 2.1
  - ruby-head
  - rbx-2
  - jruby
env:
  - "GEM=railties"
  - "GEM=ap"
  - "GEM=am,amo,as,av"
  - "GEM=ar:mysql"
  - "GEM=ar:mysql2"
  - "GEM=ar:sqlite3"
  - "GEM=ar:postgresql"
matrix:
  allow_failures:
    - rvm: 1.9.3
      env: "GEM=ar:mysql"
    - rvm: rbx-2
    - rvm: jruby
    - rvm: ruby-head
  fast_finish: true
notifications:
  email: false
  irc:
    on_success: change
    on_failure: always
    channels:
      - "irc.freenode.org#rails-contrib"
  campfire:
    on_success: change
    on_failure: always
    rooms:
      - secure: "YA1alef1ESHWGFNVwvmVGCkMe4cUy4j+UcNvMUESraceiAfVyRMAovlQBGs6\n9kBRm7DHYBUXYC2ABQoJbQRLDr/1B5JPf/M8+Qd7BKu8tcDC03U01SMHFLpO\naOs/HLXcDxtnnpL07tGVsm0zhMc5N8tq4/L3SHxK7Vi+TacwQzI="
bundler_args: --path vendor/bundle --without test
services:
  - memcached
Added a .travis.yml config and travis specific ci script. Don't install ruby-debug if running the test suite on Travis, linecache19 is the main offender, very very slow. And do not install pg if Travis is bundling the gems, pg will be setup on Travis soon. 2011-07-15 03:48:10 -04:00			`script: 'ci/travis.rb'`
Install latest bundler on Travis. 2012-03-09 16:19:55 -05:00			`before_install:`
Reverse 821525e and wrap run_generator call Ruby 2.1.0 includes the json gem 1.8.1 by default so we need bundler 1.5.1 for `bundle install` to work. To fix this reverse the downgrade to 1.3.5 and wrap the `run_generator` call with a block that resets `THOR_DEBUG`. 2014-01-02 05:06:29 -05:00			`- travis_retry gem install bundler`
`export AR_JDBC=true` on travis-ci as a before_install (but on jruby only) 2013-09-03 02:57:50 -04:00			`- "rvm current \| grep 'jruby' && export AR_JDBC=true \|\| echo"`
Added a .travis.yml config and travis specific ci script. Don't install ruby-debug if running the test suite on Travis, linecache19 is the main offender, very very slow. And do not install pg if Travis is bundling the gems, pg will be setup on Travis soon. 2011-07-15 03:48:10 -04:00			`rvm:`
Revert "Disable 1.9.3 builds until upgraded from -preview1 to -rc1" This reverts commit 8a6acc17bb8badf70e300f599bf0440ee197028c. 2011-11-01 20:41:37 -04:00			`- 1.9.3`
Add Ruby 2.0 to .travis.yml. @joshk said it's okay. :) 2012-11-17 07:44:57 -05:00			`- 2.0.0`
Only need MINOR version level to test Ruby 2.1.x on Travis cc http://blog.travis-ci.com/2014-04-28-upcoming-build-environment-updates/ 2014-05-09 16:04:50 -04:00			`- 2.1`
Test with ruby-head to make @tenderlove happy 2014-05-12 20:16:22 -04:00			`- ruby-head`
Update Travis settings for Rubinius /cc @brixen 2014-02-12 06:55:47 -05:00			`- rbx-2`
Always point to latest rbx and jruby in travis 2013-12-18 10:34:28 -05:00			`- jruby`
Added a .travis.yml config and travis specific ci script. Don't install ruby-debug if running the test suite on Travis, linecache19 is the main offender, very very slow. And do not install pg if Travis is bundling the gems, pg will be setup on Travis soon. 2011-07-15 03:48:10 -04:00			`env:`
			`- "GEM=railties"`
Split Action Pack tests in a new job on travis This will make easier to compare run time between Ruby 2.1 and trunk 2014-07-23 13:58:59 -04:00			`- "GEM=ap"`
			`- "GEM=am,amo,as,av"`
Added a .travis.yml config and travis specific ci script. Don't install ruby-debug if running the test suite on Travis, linecache19 is the main offender, very very slow. And do not install pg if Travis is bundling the gems, pg will be setup on Travis soon. 2011-07-15 03:48:10 -04:00			`- "GEM=ar:mysql"`
			`- "GEM=ar:mysql2"`
enable Travis CI irc notifications to #rails-contrib on irc.freenode.org 2011-07-26 14:17:58 -04:00			`- "GEM=ar:sqlite3"`
Enable postgres on the CI :heart: :beer: :sparkles: 2011-12-03 15:09:43 -05:00			`- "GEM=ar:postgresql"`
Allow jruby on travis allowing failures 2013-08-01 14:20:05 -04:00			`matrix:`
			`allow_failures:`
Ignore distressingly-frequent segfaults on this build Not sure what's causing them suddenly, but it seems unlikely there's much we can do about it. For the small amount of coverage this particular job gains us, it's hurting us more, by making CI failures unremarkable. 2014-06-08 10:12:01 -04:00			`- rvm: 1.9.3`
			`env: "GEM=ar:mysql"`
Update Travis settings for Rubinius /cc @brixen 2014-02-12 06:55:47 -05:00			`- rvm: rbx-2`
Always point to latest rbx and jruby in travis 2013-12-18 10:34:28 -05:00			`- rvm: jruby`
Revert "Remove ruby-head from allow_failures matrix" This reverts commit 5d2d301024cc0b17f26f6b454ac22a72f1db8a23. 2014-05-15 10:04:56 -04:00			`- rvm: ruby-head`
Enable fast_finish in the travis configuration Since rbx and jruby builds are being allowed to fail lets receive the build information early enabling this option See http://about.travis-ci.org/blog/2013-11-27-fast-finishing-builds/ 2014-01-01 21:35:51 -05:00			`fast_finish: true`
enable Travis CI irc notifications to #rails-contrib on irc.freenode.org 2011-07-26 14:17:58 -04:00			`notifications:`
			`email: false`
			`irc:`
Don't notify IRC on every single build, just failures and first success after a string of failures 2011-10-08 14:13:48 -04:00			`on_success: change`
			`on_failure: always`
			`channels:`
			`- "irc.freenode.org#rails-contrib"`
Add campfire notifications for travis 2011-12-17 10:05:14 -05:00			`campfire:`
Don't notify campfire when the build keeps passing 2011-12-18 18:37:05 -05:00			`on_success: change`
			`on_failure: always`
			`rooms:`
Change the encrypted campfire notification token 2012-12-06 12:39:13 -05:00			`- secure: "YA1alef1ESHWGFNVwvmVGCkMe4cUy4j+UcNvMUESraceiAfVyRMAovlQBGs6\n9kBRm7DHYBUXYC2ABQoJbQRLDr/1B5JPf/M8+Qd7BKu8tcDC03U01SMHFLpO\naOs/HLXcDxtnnpL07tGVsm0zhMc5N8tq4/L3SHxK7Vi+TacwQzI="`
There's no need to install test group in travis 2013-03-11 14:50:31 -04:00			`bundler_args: --path vendor/bundle --without test`
Enable memcached service on travis for running cache tests. 2013-12-21 13:46:34 -05:00			`services:`
			`- memcached`