Ok I solved it. I had to let ccnet through the firewall, and the projectTrigger is in the machine that does the automated tests. IOW, I understand now that it polls the machine that does the build, and when the build finishes with a success, it runs. Thanks!
On Apr 27, 8:45 am, Chris <[email protected]> wrote: > Thanks, but this is just yet a second way to place the project trigger > correct? > > On Apr 26, 5:46 pm, Rolando Valdivia <[email protected]> > wrote: > > > > > > > > > Take a look at "force build publisher". Add this publisher to your Build > > project and once the build succeeds the test project will be triggered. > > El 26/04/2012 16:22, "Chris" <[email protected]> escribió: > > > > I want to use projectTrigger to trigger projects on TWO different PCs, > > > say a build PC and a test PC. I want the BuildProject to trigger the > > > TestProject, so where should I put the projectTrigger condition? I > > > read docs that say the projectTrigger sets up polling, and I infer > > > that I should put the projectTrigger block in the TestProject? > > > > Also is there a user/pw access necessary to make this work? PCs are on > > > the same network/workgroup. > > > > -chris
