Skip to main content

Team Foundation Server: How to migrate TFS Version Control project by project–Part 2

If you want to migrate a full TFS collection, support is built-in. But what if you want to migrate a specific project but want to keep the source code history?

I blogged about a solution I used before by using Git as a way to move code between 2 TFS Version Control repositories. (Here is the link in case you cannot find it: http://bartwullems.blogspot.be/2015/05/team-foundation-server-how-to-migrate.html). I used this approach multiple teams with great success.

However some people who tried to do the same thing complained that the approach I described didn’t work when you have multiple branches. So time to solve this and add the misssing steps required to migratie multiple branches:

[core]

repositoryformatversion = 0

filemode = false

bare = false

logallrefupdates = true

symlinks = false

ignorecase = true

hideDotFiles = dotGitOnly

autocrlf = false

[git-tfs]

ignore-branches = False

[tfs]

touch = 1

[tfs-remote "default"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Main

[tfs-remote "Development/Feature1"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Development/Feature1

[tfs-remote "Development/Feature2"]

url = https://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Development/Feature2

[tfs-remote "Releases/Release1"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Releases/Release 1

[tfs-remote "BranchingDemo"]

url = http://newtfs:8080/tfs/DefaultCollection

repository = $/NewRepository/DevFeature1

  • Initialize the remote
    • git-tfs branch –i BranchingDemo
    • This disconnects the branch from the current remote and connect it to the new TFS server
  • Switch between all branches and execute the following commands:
    • ​git checkout "branchname"
    • git tfs branch $/TargetProject/TargetBranch --comment="branch X" 
Labels:

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

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