I had a similar idea. Under a setup like you configure I would have a CCNet project for each machine (build, test1, test2, ...) and each machine would have its own log files. Would there be a way to combine the results? I would like to keep the reporting of results as simple as possible. I intend on using the CCNet web app (and dashboard if I can't combine the results).
-- Edwin G. Castro Firing Systems Engineer [EMAIL PROTECTED] > -----Original Message----- > From: Greiner, Andrew [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 04, 2004 3:40 PM > To: Castro, Edwin Gabriel (Firing Systems Engr.) > Subject: Re: [Ccnet-user] Triggering Distributed Tests > > You could either: write a quick filesytemwatcher class and > build based on a dir update or schedule a build on the remote > machine using standard windows at job command. You would have > to be time synched in the latter scenario. We use a > filesystemwatcher that waits for an xml file. Upon finding > one we parse the xml file for success or failure and kick off > the build based on the information contained in the file. > > Thanks > > Andrew > -------------------------- > Sent from my BlackBerry Wireless Handheld > > > -----Original Message----- > From: [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > <[EMAIL PROTECTED]>; > [EMAIL PROTECTED] <[EMAIL PROTECTED]> > Sent: Wed Aug 04 18:18:04 2004 > Subject: [Ccnet-user] Triggering Distributed Tests > > I'm sending this message to both the NAnt and CCNet mailing > lists in hopes that someone will have an idea. > > I'm trying to automate a build/test process but I will need > to distribute some of the activities to multiple servers. Our > software controls a number of PCI and USB hardware devices. > We cannot setup a single machine with all of the hardware we > support due to inadequate numbers of PCI slots. > > My current plan is to setup one build server and a few test > servers. I currently have CCNet configured to build the code. > What I need is a way to trigger the test servers so they can > get the new compiled code, perform any last minute setup (COM > registration, etc.), and execute the tests. It would be nice > if I could report the test results with the build results. > > Ideally, I would have my NAnt build script trigger the test > servers, wait for test completion, and make the results > available to CCNet for the build log. I figure the test > servers could each have a NAnt script that would tell them > what do to. So, does anybody have any ideas on how I could > have a NAnt script execute a different NAnt script on another machine? > > -- > Edwin G. Castro > Firing Systems Engineer > [EMAIL PROTECTED] > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the > changes on Linux.com, ITManagersJournal and NewsForge in the > past few weeks? Now, one more big change to announce. We are > now OSTG- Open Source Technology Group. Come see the changes > on the new OSTG site. www.ostg.com > _______________________________________________ > Ccnet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/ccnet-user > > ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
