Sticky failures - aggregating modifications?

[JDAVIDI]

Greetings,

LOVING the stickiness of the build failure emails as far as everyone
continually getting the "busted" emails, but was wondering if there's
a quick n dirty means of including all of the modifications since the
failure ocurred?

I ask because while my "sticky" team members are awaiting a good
overally build, they may be inclined to fix the broken code if they
knew where it was. Problem is they're too lazy to review logs, they'd
like it in the failure email ;)

Thanks!

--jdavidi

[Ruben Willems]

Hi


if you take one of the latest builds, there is:
the modification writer task has a new property : append time stamp
http://confluence.public.thoughtworks.org/display/CCNET/Modification+Writer+Task
This will make the modification file unique, so it will not be overwritten in another build

Next, there is a new task :
http://confluence.public.thoughtworks.org/display/CCNET/Modification+Reader+Task
this reads back in modifications


so what you will have to do is the following :
° setup a modificationwriter, with appendtimestamp to true
° in the prebuild section of your config, set up the modification reader
° in the publisher section, set up a task that will delete these extra modification logs if the build is successfull


hope this clears it out

with kind regards
Ruben Willems