Continuous Integration Tool Roundup

This is a round-up of continuous integration tools, in no particular order.

  • CruiseControl: Open source, Java-based. Focused on build.
  • Cruise: Commercial. Build/test/deploy/release. Works for most platforms and languages. Free for small and open source teams.
  • CruiseControl.NETOpen source rewrite of the original CruiseControl for Java.
  • Hudson: Open source, Java-based, runs as servlet. Supports build and test. Other processes supported via plugin architecture.
  • ElectricCommander: Commercial. Does build, test, deploy.
  • AnthillPro: Commercial. Does build, test, deploy, release.
  • Continuum: Open source from Apache. Focused on build.
  • Gump: Open source from Apache. Focuses on building and testing public open source Java projects. May not be suitable for private installations.
  • Bamboo: Commercial. Build and test, with other processes provided by plugin.
  • Automated Build Studio: Commercial. Build, test and release.
  • BuildBot: Open source. Build and test.
  • CABIE: Open source. Focus on build.
  • Cascade: Commercial, free for personal use. Build and test; can be done before comitting changes.
  • Draco.NET: Open source. Focus on .NET (Windows only?) builds.
  • TeamCity: Commercial with free professional edition. Java and .NET only. Build, test, inspection (code review).
  • Team Foundation Server: Commercial from Microsoft. Team Build is the continuous integration component, tightly integrated with the rest of the system.
  • Tinderbox: Open source from Mozilla. Focuses on cross platform build and test.
  • Parabuild: Commercial, free for Open Source projects. Does build, test, deploy.
  • TapTinder: Open source. Build and test, with emphasis on test cases.
  • Pulse: Commercial, free for small teams and open source.
  • Homebrew: The pile of scripts and cron jobs you might be using to manage a daily/nightly/continuous build.

If you're in the Homebrew camp, please leave a comment: I'm curious about what the tools above are missing that force you to DIY. (I've been in this category in the past, for various reasons.)

I'd also appreciate any comments as to the relative merits of the systems mentioned above. I've only used a couple of them.

Lastly, if you use (or sell) some tool that is not listed here, please leave a comment and I'll update the list. Thanks!

Posted on 2009-01-05 by brian in tools .


I think our Parabuild is missing:

Parabuild: Commercial, free for Open Source projects. Does build, test, deploy.

Slava Imeshev
2009-01-06 03:08:48

Hi. I'm working on TapTinder . It's in early stage of development now, but I'm doing my best :-). There is old version running for Parrot VM

2009-01-06 09:37:12

Slava and mj -

Thanks, I updated the list.


2009-01-06 13:31:57

Hey Brian,

Another self-plug: you forgot Pulse (!

Jason Sankey
2009-01-07 17:34:05

Jason -

Thanks, I just added it.


2009-01-07 17:56:01

[...] Link Share the link love: [...]

CI Server Roundup | The Build Doctor
2009-01-08 15:10:52

I'm with Atlassian, makers of Bamboo. Just wanted to note that Bamboo, as well as all of our products, is free to non-profits and open source projects, so let us know if you are interested:

Ken Olofsen
2009-01-08 22:15:27

You're missing a couple from The CI Feature Matrix.

There are also some comparisons here. (And this page should be added to the links there.)

And while it isn't a tool anyone interested in one of these tools might also be interested in CITCON, both the conference and the mailing list.

Jeffrey Fredrick
2009-01-09 06:35:07

Greetings, here's another self plug as Jason so nicely puts it:.

You've left off Cruise from ThoughtWorks ( It's commercial build/test/deploy/release focused. Works for most platforms and languages. Free for small and open source teams.

There's also CruiseControl.NET ( - an open source rewrite of the original CruiseControl for Java we did for clients who refused to have any Java on their systems.

Chris Read
2009-01-09 08:54:56

One tool I use heavily is FinalBuilder ( They provide a server and scripting language. What I like about it is you can create any build workflow you want with tons of pre-canned functionality.

2009-04-28 23:28:31

We use DIY tools pieced together with Bash, TCL/Tk, and Python. We haven't gone to a packaged system (yet?) because I can usually crank out the next requested feature in less time than it takes to evaluate and install a pre-packaged system. Installation "costs" are somewhat higher in my case because introducing a third-party package at my work requires permission from my supervisor, the sysadmin, and usually at least one other manager. Most days it's easier and faster to just write the code myself. The results are functional, but nowhere near as nice as, for example, Google's BuildBot waterfall for their Chromium project.

William L. Dye ("willdye")
2009-10-17 18:58:39

" Cruise: Commercial. Build/test/deploy/release. " this information about Cruise being commercial and not free tool Conflict with information at

2012-08-29 10:04:27

@Varun: Don't confuse "Cruise" with "CruiseControl". Cruise was the original name of the tool that is apparently now known as "Go". (I'd guess that the easily confused names are why they renamed it.) I've updated the list above with the correct link and name, thanks for mentioning it. Also note that the matrix you linked to seems a bit out of date as well -- no mention of Jenkins, for example.

Brian St. Pierre
2012-08-29 12:07:37

Thanks Brian

2012-08-29 12:10:03
Comments on this post are closed. If you have something to share, please send me email.