TFS2010: Test Attachment Cleaner and why you should be using it

re: TFS2010: Test Attachment Cleaner and why you should be using it

Bhav — Thu, 18 Apr 2013 09:32:38 GMT

This tool does not do any thing instead filled up logs.

re: TFS2010: Test Attachment Cleaner and why you should be using it

Grant Holliday - MSFT — Wed, 14 Nov 2012 11:38:31 GMT

@Kim - The only change so far in TFS2012, is that most of the binaries aren't attached as part of the build - therefore eliminating a major source of the bloat.

You should still run the Test Attachment Cleanup tool that comes with the TFS2012 Power Tools.

re: TFS2010: Test Attachment Cleaner and why you should be using it

Kim Carlsen — Wed, 14 Nov 2012 10:35:44 GMT

We're running this right now, and I bet there is a lot of data that can be removed.

And I guess it will have a positivte impact on upgrade-time when we are going to upgrade to 2012.

Will there be any changes to this in TFS 2012 or do we still need to run this tool?

re: TFS2010: Test Attachment Cleaner and why you should be using it

Mike McGettigan — Mon, 01 Oct 2012 13:58:01 GMT

@Keith & Others- Make sure to use the /settingsFile: and /teamProject: command line options as the readme document is inaccurated. The document states - /settings: and /project.

re: TFS2010: Test Attachment Cleaner and why you should be using it

MattWilliams — Thu, 09 Aug 2012 18:16:53 GMT

@Grant and @Gabe, we are also having the same problem with tcmpt.exe. Our TFS database has grown to over 250GB. When I run a query, the utility will hang for about 10 minutes and then throw a timeout error.

re: TFS2010: Test Attachment Cleaner and why you should be using it

Keith — Sat, 12 May 2012 00:03:52 GMT

I've tried running the tool with the sample settings files but all I ever get is "Unknown parameter settings". Any suggestions on what I might be doing wrong?

re: TFS2010: Test Attachment Cleaner and why you should be using it

Marcus — Fri, 13 Jan 2012 20:15:07 GMT

I've run the Test Attachment Cleaner & the logs tell me it has deleted lots of stuff, however when I look at the database I see no change in its size. From SQL Server management studio I ran shrink jobs but it reports that only 5GB can be freed - the job deleted ~35GB.

Am I missing something here? Does the database now need to be re-indexed or something similar to free up the space? Any tips would be much appreciated.

re: TFS2010: Test Attachment Cleaner and why you should be using it

GrantH — Fri, 30 Sep 2011 04:40:55 GMT

@Glenn - This is one approach to keep the test result attachments small: www.tfsblog.de/.../prevent-test-results-blowing-up-your-tfs-databases

The other possibility is also to delete the results when build is deleted by changing the Build Retention policy to include “delete of Test Results”. The downside with this is we will delete both the test results (pass\fail of tests) and the test attachments. We do not have a separate knob for just the test attachment.

re: TFS2010: Test Attachment Cleaner and why you should be using it

Glenn Brown — Thu, 29 Sep 2011 14:44:29 GMT

Hi,

We ran into this issue a few weeks ago and are in the process of using the tool to purge over 100G of old test run attachments.

Going forward, is there a way to configure TFS to save only specific attachments? At this juncture the main ones we want to keep are the videos and have no interest in the DLL's etc.

re: TFS2010: Test Attachment Cleaner and why you should be using it

Grant — Tue, 26 Jul 2011 04:37:31 GMT

@Gabe - can you contact me via blogs.msdn.com/.../contact.aspx and we'll collect some more information from you. We've had a couple of people hit a similar issue recently.

Grant