pry--pry/.travis.yml

rvm:
  - 1.9
  - 2.0
  - 2.1
  - 2.2
  - 2.3
  - 2.4
  - ruby-head
  - rbx-3.69
  - jruby-9.1.13.0
  - jruby
  - jruby-head

install:
  - ruby -S gem install bundler --version 1.15.4
  - ruby -S bundle _1.15.4_ install --without docs

script:
  - ruby -S bundle _1.15.4_ exec rspec

sudo: false

matrix:
  allow_failures:
    - rvm: ruby-head
    - rvm: jruby
    - rvm: jruby-head
    - rvm: rbx-3.69
    - rvm: 2.4 # https://bugs.ruby-lang.org/issues/13537

notifications:
  irc: "irc.freenode.org#pry"
  recipients:
    - jrmair@gmail.com

branches:
  only:
    - master
added .travis.yml file now testing on: 1.8.7 1.9.2 1.9.3 rbx-2.0 jruby 2011-09-21 11:22:33 -04:00			`rvm:`
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`- 1.9`
			`- 2.0`
Remove allowed failure, switch to testing newest 2.1 Because of Ruby's new versioning scheme, testing 2.1.0 and 2.1.1 separately is overkill (like testing multiple patch levels of earlier Ruby versions). 2014-05-05 23:26:15 -04:00			`- 2.1`
Test against Ruby 2.2 on Travis CI 2014-10-14 10:07:41 -04:00			`- 2.2`
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`- 2.3`
test against 2.4 on travis 2017-05-27 13:50:50 -04:00			`- 2.4`
Add ruby-head to Travis 2013-01-27 19:39:29 -05:00			`- ruby-head`
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`- rbx-3.69`
restore #1649 version string jruby-9.1.13.0 is working, catch-all "jruby" didn't work at time of writing due to TravisCI+RVM issues. 2017-11-01 05:43:03 -04:00			`- jruby-9.1.13.0`
update 'ls' command to go through `_pry_.config`. closes #1126. 2014-02-07 23:32:42 -05:00			`- jruby`
Also test against latest jruby 2012-11-18 04:43:57 -05:00			`- jruby-head`
updated .travis.yml, should now alert #pry when tests complete 2011-09-21 11:56:59 -04:00
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`install:`
			`- ruby -S gem install bundler --version 1.15.4`
			`- ruby -S bundle _1.15.4_ install --without docs`

add spec/integration/readline_spec.rb 2014-02-03 06:35:23 -05:00			`script:`
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`- ruby -S bundle _1.15.4_ exec rspec`
add spec/integration/readline_spec.rb 2014-02-03 06:35:23 -05:00
run tests on new travis machines 2015-08-17 05:59:48 -04:00			`sudo: false`

Add 2.0.0 to Travis, allow failures for ruby-head 2013-07-26 19:26:00 -04:00			`matrix:`
			`allow_failures:`
			`- rvm: ruby-head`
workaround JRuby CI issue. 'jruby' as a catch-all often fails (not always) but pinning to a specific version seems to at least be able to run the test suite. Tracking JRuby development may be best, and then pinning to a new version of JRuby when a new version is released. It's not ideal, but at least it doesn't cause false red flags. 2017-10-08 09:09:18 -04:00			`- rvm: jruby`
Don't care about failures on unreleased jruby 2013-10-20 01:32:22 -04:00			`- rvm: jruby-head`
solve 1.9 spec failures, that occur on default Travis env 2017-09-18 20:07:52 -04:00			`- rvm: rbx-3.69`
			`- rvm: 2.4 # https://bugs.ruby-lang.org/issues/13537`
Add 2.0.0 to Travis, allow failures for ruby-head 2013-07-26 19:26:00 -04:00
updated .travis.yml, should now alert #pry when tests complete 2011-09-21 11:56:59 -04:00			`notifications:`
			`irc: "irc.freenode.org#pry"`
			`recipients:`
			`- jrmair@gmail.com`

			`branches:`
			`only:`
Use rbx-{18,19}mode as indicated http://about.travis-ci.org/docs/user/languages/ruby/ 2012-01-28 23:12:31 -05:00			`- master`