At work, I've been put into the role of TFS administrator, as the real TFS admin is leaving our organization in two weeks. We're currently using TFS 2015. I'm trying to upgrade us to TFS 2018, hopefully before the current admin leaves.
To that end, I've been reading various resources on TFS migration from TFS 2015 to TFS 2018. One resource I came across is this one Migration from TFS 2015 to 2018. This document spoke about integration between TFS 2018 and SharePoint. I had thought that integration died, after TFS 2015. Specifically, up to TFS 2015, TFS had what they called "TFS Project rooms". Sort of like a simple bulletin board type system. But Microsoft decided to break that connection, so I was lead to believe, after TFS 2015.
So, I'm wondering, since the linked to PDF speaks of integration between TFS 2018 and SharePoint, what is that about? Especially if TFS team rooms have gone away?
According to this doc about TFS 2018 and SharePoint integration:
TFS 2018 and later versions no longer support integration with SharePoint.
The SharePoint integration supports the TFS 2017 and earlier versions. In TFS 2017 and earlier versions, in addition to the team room function, this integration also has other functions.
For more detailed information about sharepoint integration , you could refer this Blog.
Since you are upgrading the TFS 2015 to TFS 2018, if you have configured the SharePoint integration in TFS 2015, you need to disable the SharePoint integration after upgrade.
In addition, in TFS 2018, we start to use Microsoft teams or slack for monitoring and communication.
Hope this helps.
Think this MS-Post might give you the answers: The future of TFS/Sharpoint Integration
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 been looking for some details about Team Foundation Server 2018:
a) How many projects can I have for collection (maximum) ?
b) Is Power Tools 2015 totally compatible with TFS 2018?
Now I've been trying to find out something related to this 2 topics in the Microsoft Documentation which is important to me.
Concerning this 2 question can anyone point me in the right direction? Because I cannot find the right documentation for this.
Thanks.
a) How many projects can I have for collection (maximum) ?
As comment mentioned clearly, currently there isn’t any official document to be referenced for the team project limits in TFS 2018.
Below is the recommended limit for Team Projects and Team Project Collections in TFS 2010, and you can refer to the numbers for your TFS structure.
200 Team Projects per Team Project Collection 50 – 200 Active Team
Project Collections per SQL Instance (range for 8GB – 64Gb of RAM)
From Martin's blog, there is a soft limit of about 300 Team
Projects per Team Project Collection in TFS 2012.
You can also reference the old document for the limits: Team
Foundation Server Team Project Limits
b) Is Power Tools 2015 totally compatible with TFS 2018?
There is no set of TFS 2017 Power Tools/Visual Studio 2017. Since from the TFS 2017 release notes.
No Power Tools have been released for TFS 2017. Most of the previous Power Tools have been integrated into TFS 2017, same with TFS 2018.
You could still use Power Tolls 2015, it's not related to TFS version. It's also compatibility with TFS 2018
Compatibility
You need to match the version of the TFS Power Tools with your Visual
Studio client. If you have VS 2015 installed, you need to install the
TFS 2015 power tools. Regardless of which version of TFS you are
targeting.
Source Link
I am doing an upgrade from TFS 2015 to TFS 2018.
I moved a collection from my TFS 2015 to my TFS 2018 as refered in the documentation:
https://learn.microsoft.com/en-us/tfs/server/admin/move-project-collection
The process was successfully done according with TFS 2018 Administration Console after I attached it.
After this I compared both collections (from TFS 2015 and 2018).
I could watch that the migration was not entirely done. In TFS 2018 I was missing this:
In my original Collection I had 3 projects. THe projects are still in there, however Project P1 used to have 6 members (4 users and 2 groups). Now it only has 4 users. The groups are missing. Any idea why?
In Project P1, In TFS 2015 I had a Visual Studio definition build. Now, In TFS 2018 I could see that the "Publish Build Artifact" is now deprecated.
In this build options I noticed in my "Multipiers" field I have this message "This setting is required". In TFS 2015 I could leave this field empty and I wouldn't get this message.
At the moment I haven't noticed any more changes, but I am worried about this.
I have more collection to migrate from TFS 2015 to TFS 2018-
How should I address this migrate process?
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/
How can I rename my Team Project that is hosted in Microsoft's Team Foundation Service? And how can I rename the area paths?
Unfortunately it is not possible in TFS 2005, 2008, 2010, 2012, or 2013. However the work to complete this has been done and it is now available on VSO and will ship in TFS 2015.
http://blogs.msdn.com/b/bharry/archive/2015/04/24/team-project-rename-available-on-vs-online.aspx
You can now rename team projects in Visual Studio Online and the upcoming TFS 2015 release: https://www.visualstudio.com/en-us/news/2015-apr-24-vso
The idea status changed to STARTED
Visual Studio Team (Product Team, Microsoft) responded On Feb 27, 2015:
Im am excited to announce that today we are planning to enable project
rename for TFS 2015. We don’t have an ETA yet for Visual Studio
Online.
If you want to see our progress, visit the Future Feature Development
page at http://www.visualstudio.com/en-us/news/release-archive-vso.
Ewald Hofman TFS Program Manager