Recently I have done a TFS upgrade from 2012.2 to 2013.4 with a hardware move. DNS settings changed to access new TFS server using the previous TFS URL. All went well and I when I started TFS 2012.2 build farm (plan to upgrade them later) it was working as expected.
Started the test controllers and when viewed in MTM Lab Center the controllers shown offline.
My plan was to upgrade the test controllers later since currently lot of lab environments in use. Event viewer in test controller indicated an error.
Restarted test controller service, restarted test controller machine, but was not helpful.
Tried clean TFS cache in Test Controller machine.
All of above was not helpful. So I decided to take a risk and reconfigure the test controller 2012.2 with the new TFS (2013.4) server. My only worry was what will happen to the existing lab environments after reconfiguring test controller.
After reconfiguring everything was smoothly working. All my previously up and running labs were working as expected.
It is great if the latest updates to TFS can be applied as and when they are released. But for a large organization it might not be sometime...
Resolve MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-rc4-004771\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found or Unable to start the process. No executable found matching command "dotnet-projectmodel-server"You might encounter compilation error in Visual Studio 2015 when a new .NET Core 1 web app is created, if you have installed Visual Studio 2...
You needed to setup dedicated machines for testing when using Run Functional Tests and you had to execute, Deploy Test Agent step and Copy...
TFS 2018 RC1 is now available and you can download it from https://www.visualstudio.com/downloads/ . Release note here explains the new fea...
If you have upgraded the TFS from TFS 2015 to TFS 2018 you will encounter a situation where your vNext build agents 1.xx are no longer valid...