Well, forcebuilding a project works. So, if I force build the Sync agent, it will sync any new files. It also seemed to trigger the code builder projects.
What I meant was that after the restart of the service, the triggers appear to work again (e.g. they will start building stuff at midnight, sync and build when code is checked in, etc.). However, a couple of days or even weeks later, it may fail again. /Anders On 19 Jan, 11:21, Ruben Willems <[email protected]> wrote: > Hi > > if you say that restarting the service solves the problem, > do you mean that when you force-build such a clean ccnet-project, it does > not work? > --> clean project does not do his job, does not start > > And after restarting the service, forcing the same clean project, it fires > right away? > > with kind regards > Ruben Willems > > On Mon, Jan 19, 2009 at 11:08 AM, Srekel <[email protected]> wrote: > > > I've got a pretty weird problem. We've got about fifty CCnet projects > > in total, spread over (currently) five different servers. Most of the > > time they work as they should, but sometimes the triggers won't work. > > > For example, we have a ProjectX Code Nightly Cleanup YBranch" which > > triggers every midnight. Here's the definition: > > > <project name="ProjectX Code Nightly Cleanup YBranch"> > > <webURL>http://ccnet/server/ab-ProjectX-code/project/ProjectX+Code > > +Nightly+Cleanup+YBranch/ViewLatestBuildReport.aspx<http://ccnet/server/ab-ProjectX-code/project/ProjectX+Code+Nightly+Cl...> > > </webURL> > > <workingDirectory>c:\depot\autobuild\logs\ProjectX Nightly Cleanup > > YBranch\</workingDirectory> > > <artifactDirectory>c:\depot\autobuild\logs\ProjectX Nightly > > Cleanup YBranch\Artifacts\</artifactDirectory> > > > <triggers> > > <scheduleTrigger time="0:01" buildCondition="ForceBuild"> > > <weekDays> > > <weekDay>Monday</weekDay> > > <weekDay>Tuesday</weekDay> > > <weekDay>Wednesday</weekDay> > > <weekDay>Thursday</weekDay> > > <weekDay>Friday</weekDay> > > <weekDay>Saturday</weekDay> > > <weekDay>Sunday</weekDay> > > </weekDays> > > </scheduleTrigger> > > </triggers> > > > <tasks> > > <nant> > > <executable>C:\Depot\autobuild\config\environment\nant\bin > > \nant.exe</executable> > > <baseDirectory>c:\depot\autobuild\config\</baseDirectory> > > <buildFile>server1_Y.build</buildFile> > > <nologo>false</nologo> > > <buildTimeoutSeconds>6000</buildTimeoutSeconds> > > <targetList> > > <target>clean_all</target> > > <target>copy_avb</target> > > </targetList> > > </nant> > > > </tasks> > > > <publishers> > > <statistics /> > > <xmllogger /> > > </publishers> > > </project> > > > Sometimes, this doesn't work. The project doesn't trigger and I have > > to start it manually when I get in in the morning, which can be quite > > wasteful as some of our projects take 5-10 hours to complete. > > > It is not restricted to ScheduleTriggers either. For example, after > > the nightly cleanup is finished, everything should be forcesynced. > > However, a couple of days ago, the forcesync CCnet project wouldn't > > trigger after I manually had triggered the Nightly Cleanup. > > > <project name="ProjectX Code ForceSync YBranch"> > > <webURL>http://ccnet/server/ab-ProjectX-code/project/ProjectX+Code > > +ForceSync+YBranch/ViewLatestBuildReport.aspx<http://ccnet/server/ab-ProjectX-code/project/ProjectX+Code+ForceSync+...> > > </webURL> > > <workingDirectory>c:\depot\autobuild\logs\ProjectX Code ForceSync Y > > \</workingDirectory> > > <artifactDirectory>c:\depot\autobuild\logs\ProjectX Code ForceSync > > Y\Artifacts\</artifactDirectory> > > > <triggers> > > <projectTrigger serverUri="tcp://ab-ProjectX-code:21234/ > > CruiseManager.rem" project="ProjectX Code Nightly Cleanup YBranch"/> > > </triggers> > > > <sourcecontrol type="p4"> > > &p4_source_Y; > > <forceSync>true</forceSync> > > </sourcecontrol> > > > <publishers> > > > <forcebuild> > > <project>ProjectX Code PS3 Build YBranch</project> <!-- > > triggers PS3 > > nobatch after it's done --> > > </forcebuild> > > <forcebuild> > > <project>ProjectX Code Xenon Build YBranch</project> > > </forcebuild> > > <forcebuild> > > <project>ProjectX Code Win32 Build YBranch</project> > > </forcebuild> > > <forcebuild> > > <project>ProjectX Code Editor Build YBranch</project> > > </forcebuild> > > > <statistics /> > > <xmllogger /> > > </publishers> > > </project> > > > We also have "sync agent" projects that check for modifications that > > often works, but sometimes just stops working. > > > In all cases, restarting the ccnet service has helped. > > > Any thoughts on this would be highly appreciated!
