Travis on non-MRI

[Kevin Menard]

Hi all,

It looks like we removed the Travis config for anything other than MRI
about a year ago. Fog 1.16.0 just shipped with a new dependency that
won't work on JRuby. I'd imagine there was a compelling reason to stop
testing other Ruby implementations on Travis, but does anyone know what
they were? I'd like to avoid similar regressions in the future if
possible.

Thanks,
Kevin

[geemus (Wesley Beary)]

I'm less convinced there was a compelling reason, I suspect it may have
just been dropped in the shuffle. We should certainly look into getting
that coverage back if possible.

Post by Kevin Menard
Hi all,
It looks like we removed the Travis config for anything other than MRI
about a year ago. Fog 1.16.0 just shipped with a new dependency that
won't work on JRuby. I'd imagine there was a compelling reason to stop
testing other Ruby implementations on Travis, but does anyone know what
they were? I'd like to avoid similar regressions in the future if
possible.
Thanks,
Kevin
--
You received this message because you are subscribed to the Google Groups "ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/groups/opt_out.

[Kevin Menard]

I've fixed or worked around all outstanding issues with JRuby and
enabled it in Travis. Going forward, any JRuby failure should be
considered legitimate. If anyone hits one and needs help working it
out, just let me know. But we should try to keep that green from now
on.



I don't use rubinius and traditionally have had problems getting it
installed, so I didn't try to get that going. I suspect a lot of the
work in getting JRuby green would work for rubinius as well. If
someone else wants to take up that charge, great. If not, we can wait
until a rubinius user chimes in.



--

Kevin





On Wed, Oct 16, 2013, at 14:58, geemus (Wesley Beary) wrote:

I'm less convinced there was a compelling reason, I suspect it may have
just been dropped in the shuffle. We should certainly look into getting
that coverage back if possible.



On Wed, Oct 16, 2013 at 12:17 PM, Kevin Menard <[1]kevin-IZBqrEfwOY1Wk0Htik3J/***@public.gmane.org>
wrote:

Hi all,



It looks like we removed the Travis config for anything other than MRI

about a year ago. Fog 1.16.0 just shipped with a new dependency that

won't work on JRuby. I'd imagine there was a compelling reason to stop

testing other Ruby implementations on Travis, but does anyone know what

they were? I'd like to avoid similar regressions in the future if

possible.



Thanks,

Kevin



--

You received this message because you are subscribed to the Google
Groups "ruby-fog" group.

To unsubscribe from this group and stop receiving emails from it, send
an email to [2]ruby-fog+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org

For more options, visit [3]https://groups.google.com/groups/opt_out.


--

You received this message because you are subscribed to the Google
Groups "ruby-fog" group.

To unsubscribe from this group and stop receiving emails from it, send
an email to ruby-fog+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org

For more options, visit [4]https://groups.google.com/groups/opt_out.

References

1. mailto:kevin-IZBqrEfwOY1Wk0Htik3J/***@public.gmane.org
2. mailto:ruby-fog%2Bunsubscribe-/***@public.gmane.org
3. https://groups.google.com/groups/opt_out
4. https://groups.google.com/groups/opt_out