October 2008
5 posts
We came, we saw, we Rumbled
RunCodeRun sponsored Rails Rumble this past weekend and offered continuous integration to participating teams. We knew going in that this would be a great way to give a useful service for test-driven teams and learn a lot about how RunCodeRun stands up to load. Things started well on Friday night and we got some great feedback from the initial teams who signed up. As development heated up on...
Oct 24th
The Rails: they be Rumbling with RunCodeRun
The starter pistol went off (metaphorically) and the Rails Rumble is off and running! For the next forty-eight hours developers from all over the country (maybe even the world?) will be vying for that most precious of geek cred — bragging rights from a well-publicized competition. Women will swoon (er maybe not), code will be written, and gods will be created. If you’re a Rails...
Oct 18th
RunCodeRun sponsors Rails Rumble 2008
Rails Rumble is this weekend, and RunCodeRun is going to help out by offering continuous integration to the first 100 teams that are interested. Rails Rumble is my favorite type of competition: the kind where people build real apps and can only win if they actually ship. Each team of up to four developers has one weekend to build a Ruby on Rails app from scratch. Last year over 90 teams...
Oct 14th
Open Source Projects are now open to everyone
We are happy to announce that all open source projects hosted on RunCodeRun are now open to the public. You can see a list of the public projects on RunCodeRun, or you can go straight to some well known projects getting continuous integration love from us: Everyone’s favorite BDD framework, RSpec James Golick’s Rails RESTful abstraction helper resource_controller Many of...
Oct 10th
Add RCov to your build in two minutes
We are big believers in the value of code coverage. Code coverage can be defined in different ways depending on language and the tool being used. With Ruby the tool is rcov and the type of coverage is “statement coverage”, also known as line coverage. Statement coverage basically shows what code was executed while your test suite ran. Although this is a coarse measurement, it can...
Oct 9th