0
votes

In preparation for an upgrade from TFS 2012 to TFS 2015, we cloned the existing TFS 2012 build server. The existing server has 4 build agents (but no controllers) installed. After cloning the existing server (server 1), the new server (server 2) has four build agents as expected. The new server was renamed and 'cleaned up' by IT. However when I delete an agent from server 2, it is automagically deleted from server 1. This is the case even when the related controller is disabled. Two questions:

Q1: Although we could delete and recreate an agent, we would rather not risk breaking or losing any vital data. How can we delete an agent on server 2 without deleting it from server 1?

Q2: We can live with re-creating the agents if we have to, but what happens if we delete the entire TFS build service from Server 2? Will we break the existing build service on server 1? And does this issue indicate we have bigger issues on the new server we need to resolve before we upgrade the build engine to 2015?

2

2 Answers

2
votes

If you are using 2012 or newer build agents, the build agents are configured to connect to server 1. The build agents though listed on server 2 won't connect to server 2 unless the agent configuration is changed to use server 2.

1
votes

Usually, after you upgrade the TFS application tier, you would install the new build service. Deleting build agent won't change your build data as the build data doesn't store in the build agent.