Hi, Is it possible to configure CruiseControl.NET to automatically perform ForceBuild every 30 minutes or so on failing projects (regardless of the cause of the failures)?
This could be used as a workaround so that our projects will eventually go back to green when the SVN server comes back. 2009/8/3 Ruben Willems <[email protected]>: > Hi > > indeed, these options will not turn the projects back to green, > but they will reduce the amount of emails / red labels. > > > If you know that your svn is out between 22:00 till 23:00 > use a filter trigger > http://confluence.public.thoughtworks.org/display/CCNET/Filter+Trigger > > > > with kind regards > Ruben Willems > > On Mon, Aug 3, 2009 at 7:37 PM, Paul Richards <[email protected]> > wrote: >> >> These options look interesting for reducing the number of emails and >> general noise made by CruiseControl while the SVN server is down. >> They don't however look like they'll help the project turn back to >> green as soon as SVN is back. >> >> >> 2009/8/3 Daniel Nauck <[email protected]>: >> > >> > Hi, >> > >> > have you tested the new options [1]: >> > >> > - maxSourceControlRetries >> > - stopProjectOnReachingMaxSourceControlRetries >> > - sourceControlErrorHandling >> > >> > of CCNet 1.4.4 ? >> > >> > Daniel >> > >> > [1] >> > >> > http://confluence.public.thoughtworks.org/display/CCNET/Project+Configuration+Block >> > >> > >> > Lennart Wagner schrieb: >> >> Hi, >> >> >> >> we have the very same problem. It would be nice if I didn't need to >> >> force the build every couple of days. >> >> >> >> I am writing this to show the developers that there is demand for a >> >> solution to this problem. >> >> >> >> Greetings, >> >> Lennart >> >> >> >> Paul Richards schrieb: >> >> >> >>> Hi, >> >>> Our SVN server is flakey and we have discovered that this doesn't mix >> >>> well with CruiseControl.NET (v1.4.4.83). >> >>> >> >>> Our project (which only has a default interval trigger >> >>> "<intervalTrigger />") will be green before the SVN server dies. The >> >>> SVN server then dies and subsequently CruiseControl flags the project >> >>> as red with a suitable error about the SVN server. >> >>> >> >>> Later when the SVN server comes back CruiseControl resumes checking >> >>> for updates to the project, sees there are no changes waiting to be >> >>> tested, but doesn't put the project back to green. >> >>> >> >>> So after the SVN server comes back online we have to manually force >> >>> all the projects which are falsely reporting red (or make a dummy >> >>> commit). >> >>> >> >>> >> >>> It makes sense that CruiseControl marks the project as red while the >> >>> SVN server is down, but it would be very handy if the status went back >> >>> to green once the SVN server is back and there are no modifications to >> >>> build (assuming of course the project was green prior to the outage). >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> > >> >> >> >> -- >> Paul Richards > > -- Paul Richards
