Skip to main content

CruiseControl and TFS:Unable to perform the get operation because it is writable

To integrate CruiseControl with TFS, we are using the TFS CCNET Plugin project on CodePlex. The plug-in works great will all versions of Team Foundation Server(although there is no official support for TFS 2010).

However last week, after importing a specific project, we got the following error message from CruiseControl:

ThoughtWorks.CruiseControl.Core.CruiseControlException: Warning AssemblyInfo.cs - Unable to perform the get operation because it is writable

What happened?

During the build, we update the AssemblyInfo.cs class to include the build number in the assembly information. Therefore we remove the readonly attribute from the file and add the build information to the file. The problem is that TFS tries to be smart about your workspace usage based on the fact that your files are readonly(although this has changed in TFS 11). So it doesn’t like that it finds some files that are not readonly inside your workspace.

As CruiseControl does not remove the workspace by default, the next time you trigger a build, the tfs get operation will fail.

How can we fix this?

Use the following settings inside your CruiseControl TFS plugin configuration:

  • deleteWorkspace=true
  • autoGetSource=true
  • cleanCopy=true

If you combine these 3 properties, the workspace is removed on every build and all existing files are deleted.

That’s it!

Popular posts from this blog

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

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.

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