To help you in decision making I can tell our teams experiences.
I was responsible for building the ci environment. We use java (maven, wicket, spring). The project is built up of multiple modules. The modules contain unit tests and integration tests. Everything is run with maven.
We tried Continuum and Cruise Control. For some reason I could not grasp the complexity of those tools. I guess I'm simple in that way.
With Cerberus everything is visible, easily configurable and you can make modifications easily. If there is some documentation missing, the source code is quite easy to read.
If you have some ruby experience in your team and want a simple, versatile and robust "build running tool" then Cerberus is a great choice.
I certainly am glad that we have Cerberus running in our ci-environment that is easily configurable with a few yml files.