Build Retention Policies in TFS2010

I noticed some interesting changes for the Build Retention Policies in TFS2010 (Beta 1):

  • possible differences between retention policy for triggered and manual builds vs private builds

    You will be able to set another retention policy on private builds: builds that are run by the enabled Gated Check-in trigger.

  • extra What to delete column

    You will be able to specify more in detail what information must be deleted when the retention policy kicks in.

3 Responses to Build Retention Policies in TFS2010

  1. Bart dk says:

    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 !

  2. 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.

  3. 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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: