_ had it building and testing an existing project in less than 5 minutes._ – MikeClark on AntHill
(I uttered that quote almost two years ago, and I'm happy to report that I now can have a project building and testing with CruiseControl in under 5 minutes. Indeed, CruiseControl has come a long way in its ease of use thanks to all the great folks in this community. All of my projects are now using CruiseControl. – MikeClark on 8/24/04)
Might be useful if we get some CruiseControlSetupTimes
This is what most people seem to like about AntHill that CruiseControl doesn't have yet:
- Easier to setup and debug (better, but ongoing)
- Multiple projects with dependencies (partially done)
- Forced builds (done!)
- Time-based scheduled builds (done)
- Web-based administration (done)
- Raw log presentation (done)
So from scratch AntHill seems to have surpassed us quite readily... All of these things (save raw log presentation, which is a good idea) were mentioned over a year ago on the lists but not yet implemented.
This is what we need:
- drastically easier setup ''(better, but ongoing)''
- multiple projects especially to reduce the number of VMs required (defer dependencies initially) ''(partially done)''
- forced builds (via JMX) ''(done!)''
- better error messages and logging ''(ongoing)''
- time-based scheduled builds ''(done)''
- web-based administration ''(done via JMX)''
- optional raw log presentation ''(done)''
- better default presentation (keep XSLT?)
- examples of more complex presentations
The quote up top is the key message.
Maybe it's easier, but it's less elegant, and harder for an engineer to understand. (I hate brightly-colored panels )
Maybe, CC can also learn from DamageControl. I didn't try it yet, as I'm quite happy with my CC setup and don't have the time left to play around. But, it might be interesting to those developing CC - to see what yet some other folks are doing.
WhatCruiseControlCanLearnFromDamageControl
