Skip to main content

TFS 2010: Cleaning test attachments

After we started to use the Visual Studio Test Professional for managing and executing our test scenario’s, I noticed that our TFS databases grew a lot faster in size.

This is not completely unexpected as you know the large amount of data you can capture while running your tests:

  • Video’s
  • Screenshots
  • Intellitrace files
  • System information
  • Event Log data
  • Test Impact data

I was looking for some possible solutions when I noticed that Microsoft already released a Visual Studio Power tool that tackles this problem.

With the Test Attachment Cleaner TFS administrators can

1. Determine which set of diagnostic captures is taking up how much space AND

2. Reclaim the space for runs which are no longer relevant from business perspective.

Usage is simple through the command line. This makes it easy to add this as a scheduled tasks on your TFS server. Some sample scenario’s are also included in the download package.

More information about the Test Attachment Cleaner on Grant Holliday’s blog.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...