Aside from using cruise control, how does this differ from what chris kimpton already has set up(http://www.lubega.com/), which runs the testsuite at least once a day and I think does hourly builds? How does your proposed system distinguish a broken build from a lengthy multi-part checkin where writing the comments on the next chunk takes 10 minutes?
<rant> I'm certainly not averse to a better system, however one of the drawbacks of the current system is that the results are mostly ignored: people will often fix problems that break the build the next day, but most people seem to feel no obligation to do anything about changes that say only break 50 or 100 tests (ok I'm probably exaggerating, but not by enough). </rant> How would your system apportion blame when there are several checkins at the same time (either interlaced or within less time than it takes to checkout and do a clean build) and the build breaks? Although I might sound negative, I actually think what chris has set up has been incredibly useful and improvements or a better system would be wonderful. thanks david jencks On 2002.09.18 09:39:37 -0400 Michael Rettig wrote: > Developers, > > I'm looking to setup a continuous integration enviroment for the JBoss > project. Does anyone know of one that exists already? > > If you don't know what continuous integration and what it can do for a > project. You can read more about it: > > http://martinfowler.com/articles/continuousIntegration.html > > I'm planning to setup a box that will detect changes to the CVS repo then > kick off an automated build to do a clean build and test of JBoss. A > public webpage will be generated that will be available to see the > current status of the build, and past builds. > > This process will help eliminate problems caused by developers checking > in code that simply doesn't compile or breaks tests. When the build does > get broken, it only takes a quick look at the web page to figure who is > responsible. > > Also, the build can be configured to automatically email anyone that > breaks the build. > > CruiseControl will be used to build the project and generate the results. > It's another sourceforge OS project hosted on sourceforge. > > http://sourceforge.net/projects/cruisecontrol > > I'm looking for some feedback on this. What do you want the build to do? > Do you want it to email you when the build breaks? What information do > you want displayed on the webpage? > > Any feedback is appreciated. > > Thanks, > > Mike Rettig > -- > __________________________________________________________ > 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 > > ------------------------------------------------------- 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
