I am using TFS 2015 U3.
I am working on Migration of TFS from 2015 U3 to TFS 2018 RC2.
We have a TFS 2015 current set up as follows:
Single App Tier- includes vNextBuild agents (Windows Server 2012 R2)
Single Data Tier - SQL server 2016 is used
If i want to configure code search server in the same application tier, is there any issue? what would be the process to do that?
Search can be used on any size physical server or virtual machine that
runs TFS 2017 or above. It can be configured on the same server as
TFS, or on a separate server dedicated to Search. When configuring
Search on the same server as TFS, you must take into account the
existing CPU utlization factor due to TFS itself. In most cases you
should consider configuring Search on a separate server.
Please go through the article below, and follow the steps there to configure Search feature:
https://learn.microsoft.com/en-us/vsts/search/code/administration
By the way, TFS 2018 RTM is available, you can upgrade to RTM version instead of RC2. Also, TFS 2018 requires SQL Server 2016 (minimum SP1), make sure your SQL Server meets this requirement.
Related
We have TFS 2013 SP 4 (our existing version) and TFS 2017 (which is under testing for we are upgrading the TFS version).
My question is : Is it possible to work and test on both the TFS at the same time with the same workspace?
Business users are able to configure the new TFS 2017 and work there. However, when they are switching back to TFS 2013 (since we have not gone live with TFS 2017), it throws an 'Identity does not exist error'.
Has anyone tried it?
Is it even possible to test this way? Or shall we have one TFS version at a time for one workspace even for testing?
Thank you.
Anant
When upgraded TFS 2013 to TFS 2017(using TFS 2013 backup) on a new Server, the two servers have the same TFS GUID, which will confuse your Visual Studio clients.
You should avoid having two TFS up & running with the same set of GUIDs. And this is usually avoided by shutting down the old TFS server after the upgrade has finished and has been tested & verified.
I've found this article about moving collections between TFS and DevOps:
https://learn.microsoft.com/en-us/azure/devops/server/admin/move-project-collection?view=azure-devops
TFS 2012 isn't listed beneath the article heading, so I'm assuming it's not possible to move a 2012 collection to Azure DevOps. Can anyone confirm or otherwise?
I guess I could just try it, but I would need to do so out of hours to avoid the disruption of detaching the collection from the live TFS 2012 server. Now I can reattach it once it has been backed-up right?!
It isn't supported, as you can find in the Azure DevOps Services Migration Guide and the Migration tool, the current oldest version supported is Tfs2018 Update 3. So you will need to upgrade to that version first.
Do note that this will also mean that you need to upgrade the SQL server database your are using to MSSQL 2016.
Is there a TFS connector for MS Flow? I only see VSTS connector.
If there is none, is there a way to connect to TFS? I would like to trgger flows when new work items / builds are created in TFS.
If your TFS server supports Service Hooks, 2015 or better, then you can configure a custom service hook receiver for Microsoft Flow. More details on setting up a service hook from the TFS side can be found here.
Your TFS server version must be at least 2015 in order to configure service hooks. Looking at the tags, your TFS version (2013) is too old, unfortunately. Given that support on TFS 2013 expires in about a year, it may be a good time to start the upgrade to TFS 2018 or a migration to VSTS.
Depending on your scenario you could look at connecting to the SQL DB behind your TFS instance directly using Flow and the on-premises data gateway. More information can be found here: https://learn.microsoft.com/en-us/flow/gateway-reference
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
We are using TFS2013 on windows server 2008R2 with sql server 2012. Now we want to move this to TFS2015... with connection to sql server 2014 (WINDOWS SERVER 2012..diff machine)...any pointers in right direction?
I recently upgraded our SQL server using this using this post as a guide. It's spot on but missing one step, at the very end before you start TFS back up you need to start IIS.
I would recommend first doing the upgrade for TFS then migrate the databases.
Based on the information here and here you should be fine restoring your backups from 2012 to 2014. Just verified that we did exactly that, moved from 2012 to 2014.