mirror of
https://github.com/pry/pry.git
synced 2022-11-09 12:35:05 -05:00
c3d51dc1dd
'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.
37 lines
555 B
YAML
37 lines
555 B
YAML
rvm:
|
|
- 1.9
|
|
- 2.0
|
|
- 2.1
|
|
- 2.2
|
|
- 2.3
|
|
- 2.4
|
|
- ruby-head
|
|
- rbx-3.69
|
|
- 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
|