I'm trying to be clever (maybe not too clever to some.) I have a list of tests (XML file) I want to run, and the list is on the build machine. I want the five test-machines to update the list as a test is run on a particular machine. So I have this scenario
- BuildProject on PC completes with success, triggers, TestProjectN's on N machines to run; the build PC has master TestList - TestProject1 on PC1 looks at master TestList and sees in needs to run Test1, so it updates TestList to indicate that it is being run by TestProject1 - Some delay seconds later, TestProject2 on PC2 looks at master TestList, and sees that Test1 is being run but another project, goes to next test, say Test2; it updates TestList to reflect this accordingly. - Some delay seconds later, TestProject1 on PC1 finishes Test1, looks at master TestList, and sees that Test1 ran,Test2 is ran by another project, and goes to next test, say Test3; it updates TestList to reflect this accordingly. I'm trying to do this so I don't hard-assign a test to a particular test machine. This way if I add/delete a test machine, the process scales itself. -chris On Apr 22, 7:26 am, Ruben Willems <[email protected]> wrote: > Hi > > can you give a bit more info on what you want to achieve? > > why would you want to have 5? servers to update a certain file? > what's the purpose of this file? > > maybe a safer way is that you place this file in source control. > each server can do an update via the source control. > > and an extra server just watches this file, and on every change do what has > to be done. > > All depends really what this file is for. > > with kind regards > Ruben Willems > > On 20 April 2012 18:42, Chris <[email protected]> wrote: > > > > > > > > > I'm setting up a test farm, using ccnet/nant running on multiple machines. > > I want each machine to update the SAME file on a REMOTE machine, so I don't > > want simultaneous access to this file. So PC1 locks and updates the file, > > then unlocks it when done. If PC2 is trying to access file while PC1 locks > > it, it pends until it's unlocked. > > > Or is there a better way to do this, like one ccnet/nant script running on > > a central machine, that then triggers the ccnet/nant script on the test > > farm to run tests?
