Hi, On Tue, Aug 22, 2017 at 07:44:42PM -0400, Eric D Helms wrote: > I am beginning to look at updating some of our test infrastructure by > re-writing Jenkins jobs into the pipeline plugin [1]. This is a new style, > with a different way of both writing and thinking about how jobs are > crafted. I've started this work by attempting to write jobs for both > Foreman and Katello [2].
+1! > ruby: 2.1, 2.2, 2.3, 3.4 > databases: mysql, postgresql, sqlite3 > > I would like to propose the following: > > 1) We drop sqlite3 entirely At least one Ruby version should get tested with sqlite3, as almost all dev setups will be sqlite and that's making it easy to reproduce test failures. > 3) We pick the most widely used Ruby version and test mysql with that Sounds OK. > 2.2 -- used in RPM production This will need to get updated for Rails 5 anyway. > 2.1, 2.3, 2.4 -- used by Debian production 2.1 is Debian/jessie, which will be dropped with Rails 5. 2.4 is not used in any Debian or Ubuntu version and it's highly likely that Debian/unstable (and thus the next Ubuntu LTS 18.04) will go from 2.3 to 2.5 directly. At the end with Rails 5 only Ruby 2.3 and 2.4 would stay and 2.5 get added in Q1/2018. Depending on the RPM situation 2.4 could get dropped theroretically again in Q2/2018. Regards -- Michael Moll -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
