Coveralls, TravisCI & CodeClimate

[BukhariH]

Might be wise to implement these three things!

They definitely do help keep development as clean and mishap free as possible!

I believe the link for adding a codeclimate open source project is:
https://codeclimate.com/github/signup

[chanks]

I'll look into this at some point, probably in the next few days, thanks.

[rurounijones]

Yes please! Travis-CI (With jruby please! 😄 ) is almost mandatory these days 😀

You should also have a look at Gemnasium to help you keep track of gem dependencies.

And get all their lovely shields in your README, it is a great way to get an overview of a project and they are all free.

Example project with all of the above: https://github.com/rurounijones/bsf-scraper

[chanks]

Sorry, didn't mean to close. Right now, the gem requires a PG::Connection object to work with, but I don't believe the pg gem works on JRuby. I'll have to look into whatever the equivalent is there and modify Que to be able to use it. Which is no problem - I'd really like to support the Ruby implementations that have no GIL (I'm looking into Rubinius right now).

[chanks]

I got the specs passing reliably on Rubinius, so I'm comfortable calling it supported. I laid some groundwork for supporting JRuby in the jruby branch, but then I started digging into how to execute queries via JDBC and I'm giving up. The interface is just terrible to work with. If anyone knows it well and wants to offer their help, I'm open to it, and I may take another crack at it sometime if there's a big enough demand, but it's not a priority for me anymore.

[rurounijones]

I think this ticket got side-tracked with the jruby / rubinius talk since it was originall raised for TravisCI, coveralls etc.

[chanks]

Yeah, I looked into those services, and they seemed like the kind of thing
that's better suited to large projects with many committers. I'm pretty
disciplined about my testing, and I don't feel like they offer anything to
my workflow right now. Maybe at some point in the future.

On Sun, Nov 24, 2013 at 6:48 PM, Jeffrey Jones notifications@github.comwrote:

I think this ticket got side-tracked with the jruby / rubinius talk since
it was originall raised for TravisCI, coveralls etc.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-29174477
.

[rurounijones]

I think it is a good thing to have for any project, even one with single committers.

• They are quick and simple to setup and require next to no maintenance afterwards.
• They provide "at-a-glance" information for potential users of your library to help them evaluate it.
• Travis-CI in particular will let you test against many different versions of ruby automatically every time.

Most I consider very convenient. Travis-CI (Or another publicly viewable CI system) I consider essential and I would be hesitant to use any project without one (especially since the barrier to entry is so low for open-source github hosted projects.)

[joevandyk]

@rurounijones we added a .travis.yml file.