If you create a setup that can be used for branches other than head I would look at using it to monitor the 3.0 and 3.2 branches.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Kevin Conner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 18, 2002 8:09 AM Subject: RE: [JBoss-dev] Continuous Integration > It's not initiated on checkin though, it polls the CVS repository > for changes and will initiate the build once the changes have settled > down. This is all configurable in cruisecontrol. > > If the build fails then cruisecontrol will email the people who checked > in code since the previous checkout. The idea is that this should be > frequent enough to catch small amounts of changes which cause problems. > > I've introduced cruisecontrol here so that we can automate builds > and testing. It has been good for us as we are a small team. > > Having said all that, I'm not sure that there is any benefit of using > this in jboss if there is already a mechanism to build on a regular > interval (which there is). If you were starting from scratch then I > would certainly recommend cruisecontrol but why change if your current > mechanism is sufficient? > > Kev > > Kevin Conner > Orchard Information Systems Limited > Newcastle Technopole, Kings Manor > Newcastle Upon Tyne, NE1 6PA. United Kingdom > Registered in England, Number 1900078 > Tel: +44 (0) 191-2032536 Fax: +44 (0) 191 2302515 ------------------------------------------------------- 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
