I have just recently started down the cruise control path on a personal project, and my company has since dumped it in favor of an Austin-based startup (Buildforge) which offers better support and feature set. Basically, I have found that if you don't use the exact version of Ant and scripts that they use, you won't get the behavior as expected. Thus, you end up doing a lot of your own coding and config work to make cruise control happy. Some is acceptable, but we practically rewrote the thing and some of our ant scripts to get it all to play nice.
On my plate still is a task to try to use their modification-set tag and from a 10 min cron job, run a target that uses that tag to determine if a build is needed. If not, it will just return quietly. Hokey, but I haven't found anything better out there unless I just use their code to create something better. I'll look into that other link that was sent out - lubega.com was it? James > -----Original Message----- > From: Kevin Conner [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 18, 2002 10:09 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [JBoss-dev] Continuous Integration > > > > Right, a build initiated on checkin is in general guarenteed > > to fail due > > to an inconsistent view of the repository. Start bitching more about > > specific problems due to checkins that developers are not fixing. If > > it continues unabated the offending developer is gone. > > 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 > ------------------------------------------------------- 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
