Cheers Ruben, the response is very much appreciated :)
On 19 Jan, 10:01, Ruben Willems <[email protected]> wrote: > Hi > > that's some request ! > > it can be done, although it will require some work on your part ;-) > > First be sure that you use the every project uses the statistics > publisherhttp://confluence.public.thoughtworks.org/display/CCNET/Statistics+Pu... > This will create a file, containing all the statistics you need, you can > alter the metrics to be gathered, but I have not done this yet myself. > the file is located in the artifact folder of the project. > > You can also use the modification writer task, to write all the > modifications per > project.http://confluence.public.thoughtworks.org/display/CCNET/Modification+... > > So now you should have the metrics and the modifications. > Ok they are per project and stored in different files, but you get them > automatically. > > Now for trigering : > you can add a ccnet project for this 'Make Week Reports', that is sheduled > to run at monday 06:00 (schedule trigger) > this will run a program that creates the reports. Making it run after the > last checkin, is not possible in my opinion. > Define 'last build' ;-) > > So I would suggest that it will run at 06:00, and the managers can have it > at 06:05 am, normally managers like this kind of stuf ;-) > > now you must write a program that makes the report of these files. > Should not be that hard. > > with kind regards > Ruben Willems > > On Mon, Jan 19, 2009 at 10:46 AM, CinnamonDonkey < > > [email protected]> wrote: > > > Hi All, > > > I have been asked to configure CC.Net to generate weekly digest > > reports of the installations activity. This report should have a > > format something like this: > > > Header. > > Summary of weeks builds (Data, Time, Change List Used, Outcome, > > Defect Metrics for the week). > > Detailed Report per build for the week (Date, Time, Change List > > Used, Outcome, Modifications, Test Results). > > > My Team Lead seems to be very keen on this feature, suggesting that > > all team leads should receive this weekly digest report so that they > > can keep track of the project status and the staff working on the > > project. > > > To be honest though, I can't for the life of me think where to begin > > to provide this functionality within the scope of what CC.Net > > provides. > > > The only why I can think to do this is to collate all the metrics > > myself and run a Python script to parse the results once a week. > > > This leads to another problem... how to trigger the event which needs > > to occur after the last build of the week. > > > Any ideas? > > > Cheers, > > Shaun.
