Comments on: Build Retention Policies in TFS2010 http://intovsts.net/2009/10/11/build-retention-policies-in-tfs2010/ blogging about the current and upcoming release(s) of Visual Studio Team System Thu, 26 Jan 2012 12:21:45 +0000 hourly 1 http://wordpress.com/ By: pietergheysens http://intovsts.net/2009/10/11/build-retention-policies-in-tfs2010/#comment-1349 Wed, 05 Oct 2011 15:54:19 +0000 http://intovsts.net/?p=297#comment-1349 Bart,

note that the latest TFS Power Tools release (August 2011) now also contains a “Test Attachment Cleaner”.

http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f

Pieter.

]]> By: pietergheysens http://intovsts.net/2009/10/11/build-retention-policies-in-tfs2010/#comment-1348 Wed, 05 Oct 2011 14:05:35 +0000 http://intovsts.net/?p=297#comment-1348 Bart,

the decision to preserve the TestResults by default was taken due to the fact that “historic” Test Plans became “incomplete”. Test Management often requires to keep test results a bit longer than a few days …

The default “retention policy” setting in new build defintions cannot be changed. You could change the existing build definitions via the TFS API ;-(

Good luck!

Pieter.

]]> By: Bart dk http://intovsts.net/2009/10/11/build-retention-policies-in-tfs2010/#comment-1347 Wed, 05 Oct 2011 13:50:36 +0000 http://intovsts.net/?p=297#comment-1347 Pieter,

Any idea why they changed the default “What to delete” from All to All- Testresults and where we can change this default ?

http://support.microsoft.com/kb/2182621

We do not want to trigger a program after build creation, but we do want to change the default. Because now our TFS database is growing very .. very fast !

]]>