-> If you were starting from scratch then I > would certainly recommend cruisecontrol but why change if your current > mechanism is sufficient?
The current mechanism is sufficient, but it could be much better. The key distinction here is that CruiseControl ties checkins to build failures and presents this information in a public web page. On prior projects, when I broke the build (yes, I admit it) the build itself would notify me via email within minutes, then if I didn't fix it, a steady stream of developers would call me to tell me what an idiot I am for breaking the build. They knew I broke the build because the very public web page had the results of the broken build and my list of checkins attached to it. No mystery there. In a very short amount of time, I learned not to break the build. This was true of all the other developers too. Do you have any current mechanisms that can give you this rapid feedback? When things break how do you address accountability? How long does it take? -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
