Looking for circleci/jruby:9.2.10-browsers container. Is there a way for us to kick off a build for this new version of JRuby?
latest tag will provide JRuby
9.2.9, but if you need 9.2.10 specifically there is a quick fix I can suggest. The following commands (which you can add in your config.yml) will replace
wget https://repo1.maven.org/maven2/org/jruby/jruby-dist/184.108.40.206/jruby-dist-220.127.116.11-bin.zip unzip jruby-dist-18.104.22.168-bin.zip sudo rm -r /opt/jruby/* sudo cp -r jruby-22.214.171.124/* /opt/jruby/
Your work-around does work, thank you.
However, I see there was a new build 14 hours ago tagged with 126.96.36.199 but that still seems to contain 188.8.131.52
The latest official JRuby image does have 184.108.40.206
➤ docker run -it jruby:latest /bin/bash 125 ↵ root@b3873c1fd280:/# ruby -v jruby 220.127.116.11 (2.5.7) 2020-02-18 fffffff OpenJDK 64-Bit Server VM 25.242-b08 on 1.8.0_242-b08 +jit [linux-x86_64]
So something isn’t quite right here in the CircleCI image
➤ docker run -it circleci/jruby:9.2.10-browsers /bin/bash Unable to find image 'circleci/jruby:9.2.10-browsers' locally 9.2.10-browsers: Pulling from circleci/jruby # ... circleci@3fda17c06f5b:/$ ruby -v jruby 18.104.22.168 (2.5.7) 2019-10-30 458ad3e OpenJDK 64-Bit Server VM 25.242-b08 on 1.8.0_242-b08 +jit [linux-x86_64]
I see the circleci/jruby container has been updated and now has 22.214.171.124 so the workaround is no longer needed.