Thanks to tkellen for the initial setup, Sequel now uses TravisCI as a backup for testing. I don't plan on changing my current before-push testing strategy, but using TravisCI should provide additional assurance. Through the use of TravisCI, I did find a couple of issues in Sequel's specs that needed to be fixed, as well as bugs in other libraries that I've added workarounds for.
I'm currently testing the core, model, plugin, sqlite, postgres, and mysql specs on 10 separate ruby interpreters on TravisCI. See http://travis-ci.org/#!/jeremyevans/sequel/builds for build information. Currently, jruby and rbx 1.9 modes are failing in some of the adapter specs. I don't plan on adding workarounds for those failures as I think they are bugs in the interpreters, but if anyone else wants to take a closer look, please do so. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/IKUQh0EIBd8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
