Like all of us here at Relevance, I’m very excited about RunCodeRun, the hosted continuous integration service we’ve been building. This week I wrote runcoderun-badges, to make it easy to display the build status of our open-source projects on any web page we choose. One of the core benefits of continuous integration, after all, is accountability—and how better to hold yourself accountable than by showing your integration status to the world?
I started with Dr Nic’s wonderful GitHub badges (it would’ve been foolish not to!) but a lot has changed. I’ll keep this up to date as RunCodeRun evolves.
If your open source projects are already on RunCodeRun, check out the runcoderun-badges README for information on adding a badge to your blog. (And if your projects are not yet on RunCodeRun, drop by and request an invitation.)
Update: As Dan Manges discovered, these badges don’t play nicely with the GitHub badges on the same page. The problem appears to stem from the way each badge depends on JQuery. For now, consider using just the RunCodeRun badge (you can get to a project’s GitHub repository from its page on RunCodeRun), but I know that’s not a good long term solution, so I’m working to fix the problem.

Comments
This is cool – thanks. I get an error if I try to display the github badge and the runcoderun badge on the same page. They both work individually. If I get a chance to look into why I’ll post another comment.
Thanks, Dan. I’ll look into that. I’m sure the problem is because one is based on the other and there’s some failure of namespacing (either in JavaScript or CSS).
Nice widget, very good idea, especially for open-source people. I have a lot od respect for people from open source. This is fantastic comunity, far away from corporation. I like it.
Does anyone else use Prototype with this badge? I get errors on my blog such as element.dispatchEvent is not a function. Possible a conflict with JQuery. Was wondering if that was just me or is mixing the two not a good thing.
Ken: Mixing it with prototype will probably produce errors right now. There are ways to fix that (with jquery noconflict mode), but we’ll have to update the badge with that fix.
Thanks for letting usk now.