From 3da1d36565e5e5d94f052b60f1c78e59f5500a79 Mon Sep 17 00:00:00 2001
From: Gonzalo Rodriguez <grzuy0@gmail.com>
Date: Mon, 19 Mar 2018 14:19:37 -0300
Subject: [PATCH] Fix jruby CI builds

For jruby we need to stick with rubygems 2.7.4 until
https://github.com/rubygems/rubygems/issues/2188
is fixed and released.

Without this workaround, for jruby builds, rubygems
activates jruby stdlib minitest (v5.4.1) instead of the
bundled version (v5.11.3).
---
 .travis.yml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index b019a2d..7efc8d3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -10,7 +10,14 @@ rvm:
   - jruby-9.1.16.0
 
 before_install:
-  - gem update --system
+  # For jruby we need to stick with rubygems 2.7.4 until
+  # https://github.com/rubygems/rubygems/issues/2188
+  # is fixed and released.
+  #
+  # Without this workaround, for jruby builds, rubygems
+  # activates jruby stdlib minitest (v5.4.1) instead of the
+  # bundled version (v5.11.3).
+  - if [ "$TRAVIS_RUBY_VERSION" = "jruby-9.1.16.0" ]; then gem update --system 2.7.4; else gem update --system; fi
   - gem install bundler
 
 gemfile: