Have you had a chance to look at our Parabuild at http://www.viewtier.com/products/parabuild.htm ?

Have you tried Hudson http://hudson.dev.java.net

Actually we did take a look at it. It's certainly an impressive project, but in the end as you say it was a one-man show and was behind a bit in features. That being said, the distributed build functionality was very impressive and one of the things lacking from Bamboo. In our case, we don't really need distributed builds, but I know that the Atlassian is working hard on getting the same functionality into Bamboo.

In any case, I think we're starting to see quite the competition in the CI space. Between Bamboo, Team City, and Hudson a lot of innovation is coming out and it'll be exciting to see how it progresses. It's good to see such a focus on CI now, when previously there was almost none.

My initial test with Bamboo was fairly good, and had little problems, but the main issue with us is all our tests that are not JUnit tests.

This certainly has been reiterated in the Bamboo forums and on the Bamboo JIRA. One of the really nice things about Bamboo (and all Atlassian projects really) is that it is plugin based. Right now, they support JUnit results and Clover results. I can't imagine that we won't start seeing results pages from other test frameworks such as FitNess and Watir, as well as coverage results from things like Cobertura and Emma.

Atlassian certainly welcomes community development of these plugins, and my own experiences toying around with the plugin framework tells me that this wouldn't be too hard to do. But in the mean time, I know that they're trying to add some important functionality elsewhere in the project and will eventually get back to expanding the plugin selection.

We are using Bamboo to build Spring IDE (http://springide.org/bamboo) since it was an early beta. It runs complex Eclipse PDE builds without any problems.

I think the same about Bamboo as Ben: It is by far the easiest and most convenient CI tool out there. And it looks really nice, if that matters.

Talk about a small world, I had no idea you all were using Bamboo as well. And after using make, ANT, and CC for many years, I can say that looking nice does matter.

Fate is telling me it's time to switch. I looked at Bamboo a few weeks back but it just ended in a ticket asking for SSPI support. That ticket was closed today so I'll be downloading Bamboo again.

CI has been waiting for a company like Atlassian to make something inexpensive and clean.

it's open-source and free, has a nice UI (though not as sophisticated as Bamboo's), a plugin system, and integrates with JIRA (via a plugin) and various other things.

It is still low on the radar at the moment (it's fairly new and a one-man-show until recently), but it wipes the floor with cruisecontrol/continuum/etc. The guy who runs the show is one of the JAX* dudes from Sun and they use it to build many many projects (glassfish, all the JAX*, etc). I hear that Lucene recently switched to it.

Oh, and it supports distributed builds!

My initial test with Bamboo was fairly good, and had little problems, but the main issue with us is all our tests that are not JUnit tests. I might do another run with Bamboo, but initially I could not get our Fitnesse tests to run. We also do CI on Watir tests, so I'm really missing a CI tool that would cover Fitnesse and Watir too.

I think the same about Bamboo as Ben: It is by far the easiest and most convenient CI tool out there. And it looks really nice, if that matters.