CI failures on 1.9.3 with Bundler 1.8.0

Over the past day we've seen some CI failures on Ruby 1.9.3 (and usually
the postgresql subset, for some unknown reason) since Bundler 1.8.0 has
been released.

It seems there's an issue with native extensions and parallel
installation (https://github.com/bundler/bundler/issues/3385), so I've
reverted jobs to 1.7.13 for the meantime.

··· -- Dominic Cleal Red Hat Engineering

The root cause seems to have been an older version of Rubygems itself,
so this is being updated across our rvm installations
(https://github.com/theforeman/foreman-infra/commit/0524c712bfaf9624cd35afd7fb4cc9fc4dab5ae6)
and then we can go back to Bundler 1.8.0.

Please let me know if you see any gem/bundler related issues that may
have resulted from the update.

··· On 11/02/15 10:02, Dominic Cleal wrote: > Over the past day we've seen some CI failures on Ruby 1.9.3 (and usually > the postgresql subset, for some unknown reason) since Bundler 1.8.0 has > been released. > > It seems there's an issue with native extensions and parallel > installation (https://github.com/bundler/bundler/issues/3385), so I've > reverted jobs to 1.7.13 for the meantime.


Dominic Cleal
Red Hat Engineering