You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of Logstash 6.0 just around the corner we want to take the opportunity to upgrade to JRuby 9k, since 1.7 is EOL and a lot of gems are now breaking under 1.7 because they explicitely require JRuby 9k in their gemspec.
I've created a PR on the beats input that makes sure we test the following matrix.
Release Gems + JRuby 1.7.25
Unreleased gems on LS 5.x + JRuby-1.7.25
Logstash Master + JRuby-1.7.25
Specific JRuby 9k Logstash feature branch + JRuby-1.7.25
What it does?
It make sure we test a plugin with the right jruby and also unreleased logstash branches, you can see an example run at https://travis-ci.org/logstash-plugins/logstash-input-beats. I've marked the JRuby 9k as a non-fatal job, but we will be able to query travis later to create a meta issue of problematic plugins.
There is some shell scripts to make sure we checkout the right branch, I've also added debug statement in the jobs itself to help debugging what version we are actually testing. Like this:
With the release of Logstash 6.0 just around the corner we want to take the opportunity to upgrade to JRuby 9k, since 1.7 is EOL and a lot of gems are now breaking under 1.7 because they explicitely require JRuby 9k in their gemspec.
TODO
.travis.yaml
file to build JRuby 9k. #7126java.time
for timestamp instead of joda. Use Java 8 Time instead of Joda in LS and any plugins. #7149cc @guyboertje
The text was updated successfully, but these errors were encountered: