Eric H. Johnson wrote: > Jeff et al, > > It looks like I was checking things in at the same you were. How are the > compile farm errors generated? All of my stuff is now checked in, but the > last thing I checked in was the updated submakefile, without which it would > not make correctly. How do I check now to see that everything builds > correctly? > > It builds automatically after every commit. It checks every five minutes, if there has been a commit (in any branch) it does a cvs up in whatever branch(s) the farm is configured to build. If the cvs up shows a change, it does a build.
I just recently changed it to do an incremental build (./configure; make) instead of a full build (./configure; make clean; make) if its been less than 12 hours since the last full build. The full builds on three virtual machines and the real machine all at once were getting really slow. I may soon change it again, so that an incremental build will just do "make". Jeff tells me that if configure or configure.in has changed, make will automatically do ./configure. Success and failure are reported to the webpage, failures and the first success after a failure are to the IRC channel, and failures only are reported to the commit list. I've been thinking that maybe the first success after a failure ought to be reported to the commit list as well. Regards, John Kasunich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
