The more I think about it the more I like the idea... Can you make it so only the relatively quick unit tests are run on each build and emails are sent to the list and recent committers if say the broken-test count increases by more than 5 or the number of tests decrease by more than 5? (breaking tests by preventing them from deploying results in a decrease in test count rather than in increase in broken test count). I think running the full test suite might take too long after each change...
thanks david jencks On 2002.09.18 11:32:30 -0400 Matt Munz wrote: > From what I've seen of CruiseControl, I think it's a useful tool, and if > Michael or someone else wants to set it up, I'll use it. > > As far as I can tell, both the lubega and cruise control systems operate > remotely. I don't see any reason why they can't coexist. > > Nothing wrong with a little diversity, right? > > - Matt > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin > Conner > Sent: Wednesday, September 18, 2002 11: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 > > ------------------------------------------------------- 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
