I am running an automated diff ( difference ) script across two SCM branches of what is meant to be the 'same' data.
The requirment is to email out to users the files that have differences across different branches daily so they can rectify inconsistency. Since it take about 5 hrs to run the diffs it's not practical to or desired (email spam) to run continuously. The rate of change is high and even running it daily can result in thousands of modifications. Further, if CC.Net falls over due to lack of memory then by the time I've rectified at let it run again even more modifications can build up and can result in a continual out of memory cycle. IIRC this sort of problem with a large number of modifications can also occur when you run a new CC project for the first time. Best Regards, Spurtus. On Oct 1, 7:38 pm, Ruben Willems <[email protected]> wrote: > Hi > > maybe a stupid question : why only integrate after thousands of changes? > that kind of bypasses the idea of *Continous* integration > > with kind regards > Ruben Willems > > On Thu, Sep 30, 2010 at 11:28 AM, Spurtus <[email protected]>wrote: > > > > > I've tried removing some of the highly repeated comments in the > > P4HistoryParser as it can run out of memory. > > > But sometimes there are so many modifications it will still run out of > > memory. Has anybody any advise for preventing Crusie Control running > > out of memory in th P4HistoryParser or in general elsewhere when there > > there are thousands of modifications. > > > Thanks! > > > Spurtus.- Hide quoted text - > > - Show quoted text -
