yes, the explanation is further clarified other doubts had in mind.
Thapliyal Akshat wrote:
It's the mediator between your build tools and the deployment environment. Either you do it manually or through CC.
If I just see this point, either using Maven / Ant some tasks definition can be written which will do the automatic deployment work also after checking out code and doing compilation on the build.
so, would you clarify this like how CC is better than maven/Ant in this specific area?
except above, like David told commits merges and build failure reporting, I have found some good points on top is that in Cruise Control you get a web control to see, compare and find out various commits differences and can easily review the changes done and let CC to control the stability of the builds also.
further inputs and suggestions are appreciated, and looking forward to take a good suggestion based on this conversation.