Skip to main content

Azure DevOps– Obsolete check-in policies

Today I had to make a fix in an old project that was still using Team Foundation Version Control (TFVC). It immediately made me appreciate GIT a lot more but that is not what I want to talk about today.

After making my changes I had to check-in my changes (remark: commit my changes if you want to use the GIT terminology). One of the features that TFVC had to offer was the concept of check-in policies, rules that could be checked and validated before you can check-in your changes in the central source repository.

This was a feature we used a lot to improve the quality of the code and capture some mistakes as soon as possible. This time when I tried to check-in my changes, I noticed the following warning in Visual Studio:

Obsolete policies are being applied and should be updated.

This is because the way that TFVC check-in policies are stored in Azure DevOps has changed. This migration is required for keeping TFVC check-in compatible with the future Azure DevOps versions. The good news is that for every old policy, a new policy is created that guarantees future compatibility. For the time being, both old (Obsolete) and new policies remain valid and functional.

Let me show you how to update your policies:

  • In Visual Studio, open the Azure DevOps overview screen. Click on Settings.

  • On the Settings screen, click on Source Control under the Team Project settings.

 

  • On the Source Control Settings screen, go to the Check-in Policy tab and click on Remove for each of the obsolete policies.

 

  • Afterwards click on Add… and choose the non-obsolete alternative of the check-in policies that you just removed.

 

  • That’s it!

More information

Azure DevOps service updates and integration improvements | Microsoft Learn

TFVC Policies Storage Updates - Azure DevOps Blog

Labels:

Popular posts from this blog

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

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

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...
Read more