RunCodeRun is a hosted continuous integration service for Ruby projects on GitHub and is developed by Relevance.
Why a hosted continuous integration service? Rob Sanheim in his announcement blog post:
Social source control has been a major factor in open source for a long time, but GitHub really elevated the game. It makes setting up source control for your project dead simple, and eliminates the front-end IT pain of managing a project. That still leaves continuous integration, the back-end IT pain, up to the team. We want CI to be as automatic, and as easy, as source control, and the way to do that is a hosted solution.
RunCodeRun is still in a private beta, but you can take a look at various open source projects that are being built or apply for an invite.
InfoQ talked to Rob Sanheim to learn more about RunCodeRun: The public projects all seem to use GitHub. Is RunCodeRun only usable with a GitHub project?
We're dogfooding RunCodeRun, starting first by building the system we want to have and use. We are all huge users and supporters (and paid users!) of GitHub, so that led us to starting with them. We have plans to go beyond GitHub and Git itself, but for right now its just GitHub.
Can you tell us something about how RunCodeRun is implemented?
We use Rails on the front end, with our own custom builders on the back end. We are using Amazon's EC2 to scale builders up and down as need dictates.
Is it possible to build a project with different Ruby versions? And when will it be available for the general public?
Yep, all these things are coming as soon as we can get to them.
Besides just building and running tests (even against multiple Rails versions), RunCodeRun can also measure code coverage with rcov.
For more information, subscribe at the site or read the RunCodeRun blog.