{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Evening l夕情丶 的问题《Migrate Project to TFS2018》','https://www.manongdao.com/q-907282.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I have two TFS servers - one running 2008 and the other running 2018. I need to move one project (not all) from the TFS 2008 server to the new one. I only need to migrate the source code but would like also maintain all version and checkin history. Is there an upgrade process or utility that can achieve this? Thanks
相关问题
- Getting error: File extension specified '.webt
- Using TFS command line tf.exe how can I copy a rep
- TFS Power tools Migrate doesn't actually migra
- What is the difference between tfpt scorch and tfp
- TFS 2017 Agent: and error occured while sending th
相关文章
- Is it possible to do a “destroy history” in TFS?
- How do I make a TeamCity build appear in the TFS B
- TFS vs. JIRA/Bamboo/SVN [closed]
- Why doesn't my .tfignore file ignore my packag
- Is it possible to create a docker container from T
- How to Move TFS 2010 Build Definition between Proj
- How to fix TF246017 The Team foundation server cou
- How to open TFS Power Tools - Alerts Explorer
If you want to maintain all version and check-in history. The only way is upgrading TFS server 2008 with database.
Direct upgrade to Team Foundation Server 2018 Update 2 is supported from TFS 2012 and newer. Since your TFS deployment is on TFS 2008, you will need to perform some interim steps before upgrading to TFS 2018 Update 2. Please see the chart below for more information.
If you want to change the hardware which is a restoration-based move, and you should never combine the two move types. First complete the hardware move, and then change the environment: https://docs.microsoft.com/en-us/vsts/tfs-server/admin/move-across-domains?view=tfs-2015v
Would it be best to do the upgrade in-place before moving hardware/domain?
You could do in place upgrade, or move to new hardware. If you're upgrading in place, consider doing a dry run of your upgrade in a pre-production environment, and make sure the system environment is meet.
Are there any particular pitfalls I should be wary of?
Before upgrade, you can read this article first, and be sure you have full backup of your database.
You'll have to migrate from TFS 2008 to TFS 2018, at which point you can delete whatever projects you want from TFS 2018. That's going to be the easiest way to do it. Besides there being no really solid work item migration tools, everything has changed significantly since TFS 2008, including things like APIs, work item layouts, fields, features, etc. You're looking at a miserable process to get data from 2008 to 2018 without signficant effort.
The TFS 2008 -> TFS 2018 upgrade process is going to be a bit fiddly, because you can't go directly from 2008 -> 2018, you'll have to go from 2008 to 2012, then 2012 to 2018. However, it's totally supported and is relatively painless, outside of having to do it in multiple steps.