The RunCodeRun Blog: Archive

Saying Goodbye to RunCodeRun

It is unfortunately time to close the doors, turn out the lights, and shut off the servers at RunCodeRun. After nearly a year and a half of builds, thousands of awesome projects, a tremendous amount of effort, and quite a bit of learning, we’re ready to say that RunCodeRun has run its course. As of April 15th, RunCodeRun will be no more — not for paying customers, and not for open...

Mar 21st

1 note

RunCodeRun Returning to Open Source Only

RunCodeRun originally launched as a free service for open source developers working with Ruby and Rails. Since our initial launch, we’ve expanded to support other development environments, most notably Clojure (and Java, more generally). Our community of developers has grown tremendously, with thousands of people using RunCodeRun to sanity check their code daily. Along the way, we also...

Feb 9th

3 tags

Campfire Notifications Updated to use API Token

We have updated our Campfire build notifications to work with the new Campfire API. Any projects previously setup to use the old form of authentication have been disabled and now require an API token. The new API token should be entered in the Campfire notifications screen as seen below. Note: We recommend setting up a separate “build-only” user and using that API token for...

Jan 2nd

The Basic Plan, New Signups, and the Holiday...

As RunCodeRun matures and as we have continued to gain users, we have reached our current capacity level for the Basic Plan. With the holidays approaching, we are taking the step of temporarily disabling new signups for the Basic Plan. This will allow us to reconfigure our resources for the new year. In the meantime, our Premium and Walk Among the Gods plans are still available and will continue...

Nov 13th

Getting Your RunCodeRun on with Geektool

Are you using GeekTool? If not, download it! It is a very cool tool to help you keep track of what’s going on with your Mac. Now you can combine the power of Geektool with the RunCodeRun API. Head over to Github and checkout Aaron Bedra’s clj-runcoderun-radiator. Give it a shot on the command line by running ./geektool Notice that you get a list of the Relevance open source...

Sep 23rd

Get to Green on Ruby 1.9

These projects have passing test suites on Ruby 1.9. Come and see how your code fares. Ruby 1.9 is a terrific step forward from 1.8, and it is high time to start looking at moving your code there. (If you’re a Rails developer, you’ve probably heard that Rails 3 won’t just work on Ruby 1.9; it will prefer Ruby 1.9.) Of course, it isn’t just about your own code. What about...

Sep 15th

Blue Ridge Pro Tip: Trust the Wiring, Test the...

A Common Problem: Testing jQuery Event Handling The prevailing style in jQuery is to inline your event handling like: $(function(){ $("#some-id").click(function{ $(this).attr("some-attribute", "some new value"); }); }); And so, most new users of Screw.Unit (and Blue Ridge) try to write specs like: //do NOT do this! it("does something", function(){ // setup HTML fixture here ...

Sep 2nd

Announcing the RunCodeRun Basic Plan

We are pleased to announce that the RunCodeRun Basic Plan is now available. Targeted at solo developers, the Basic Plan costs $19 per month and supports up to three private projects. Unlike the Premium and Walk Among the Gods plans that provide a dedicated server for each account, Basic Plan private builds run on shared RunCodeRun build resources. So drop by our list of plans and sign up for...

Sep 1st

Now, with PostgreSQL support

We’ve been supporting builds on SQLite and MySQL since launch, but we’ve now added support for PostgreSQL (version 8.3) as your build-time data repository. Switching is dead simple: edit your project, and choose PostgreSQL from the “Database” dropdown: That’s it — no other craziness needed. PostgreSQL at your disposal. Also, check out our knowledgebase...

Aug 24th

Now Supporting Campfire Notifications

Because builds can’t fail loudly enough or embarrass you in enough places, RunCodeRun now supports politely alerting you to your FAIL through Campfire. No need to install anything into your build, just tell RunCodeRun “Yes, ma’am, can I have another!” First, log in and edit your account profile: Then, click on the “Notifications” tab and fill in your...

Aug 17th

RunCodeRun now supports private builds

We are pleased to announce that RunCodeRun is now accepting private builds. This means that you can now connect your private repositories on GitHub to RunCodeRun for your continuous integration needs. You can drop by our list of plans to see which best suits your situation. We feel it important to note that RunCodeRun remains, as always, free for open source developers. If you are already an...

Aug 4th

TDD in a functional language: Uncle Bob's Bowling

/* Unobtrustive Code Highlighter By Dan Webb 11/2005 Version: 0.4 Usage: Add a script tag for this script and any stylesets you need to use to the page in question, add correct class names to CODE elements, define CSS styles for elements. That's it! Known to work on: IE 5.5+ PC Firefox/Mozilla PC/Mac Opera 7.23 + PC ...

Jul 21st

4 tags

It's Okay to Break the Build; It's Not Okay to...

When should your Continuous Integration service notify you about the results of a build? When we originally implemented email notifications for RunCodeRun, we thought to ourselves, “We get too much email as it is. Let’s not send an email after every build; let’s just send notifications when the build status changes. You know, when the build breaks, we’ll obviously want...

Jul 17th

4 tags

Building Java Projects with RunCodeRun.com (or...

RunCodeRun is known for free open source builds, but did you know it builds Java as well? RunCodeRun still assumes that you are using Rake instead of Ant, but thats easily remedied with a Rakefile that forks an Ant build (note that there are many resources for building Java with Rake or other JRuby based tools as well). Since Ant isn’t available on RunCodeRun by default, you’ll need...

May 21st

1 note

Testing against multiple Rails versions

It should be obvious from the fact that we built RunCodeRun that we at Relevance believe strongly in continuous integration. CI is more than just testing—it gives you something qualitatively different, over and above what good testing discipline gives you. One example of that is what Chris Eppstein (one of the Haml and Sass team) did last week. He’s using RunCodeRun to test the...

Feb 17th

Email outage - last Thursday until Saturday

Late last week, starting on Thursday, February 5th, we experienced an email outage due to some internal email notifications going haywire. This issue was fixed on Saturday. The outage meant that you may have missed build notifications during this period, so it’s possible your build was fixed or broken without your knowledge during this time. We apologize for any inconvenience this...

Feb 10th

3 tags

It's Okay to Break the Build

“My name is Stuart Halloway, and I believe it is OK to break the build.” Several developers have recently asked me “How should developers who break the build be punished?” With only that information, my answer is easy: They shouldn’t. Of course breaking the build is not a good thing, but let me make a couple of hypothetical examples to demonstrate the...

Jan 22nd

2 notes

Disabled projects

You can now disable projects in RunCodeRun. “Disabling” basically means that the project and its history will be maintained, but future builds will not run. Any future pushes to that project will be ignored silently. We will be adding some more smarts to the project listing soon, and disabled projects will not show up in the default view when those changes are in place. So if you...

Dec 10th

Post-Receive Changes from the GitHubs

GitHub recently rolled out a change to allow multiple post-receive urls per project. This allows you to integrate with as many services as you like from GitHub. Our instructions for getting started with Github integration have been updated to reflect this change. More importantly, GitHub seems to have lost many of the pre-existing post-receive urls in the transition. If you’ve noticed...

Nov 21st

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

RunCodeRun has been jQuery-ised and moved to...

We just deployed a new release and moved to a new cluster hosted by Contegix. Contegix is a top notch managed host, and will free us up from day to day sysadmin tasks to concentrate on busting features out for RunCodeRun. More importantly, this release also finally pushed out a bunch of features and fixes that were waiting. These include: pages auto refresh with ajax, so you don’t...

Sep 29th

First post!

That is all. Nothing to see here. Move along.

Sep 12th