We need to synchronize several projects hosted on Visual Studio Team Services with our on-promise TFS 2015 Update 2. The ultimate goal of TFS is to have CI/CD happening within company for all external projects. However, we don't want to interrupt developers for whom using VSTS will be better choice then TFS.
However, I can't find any solution for TFS to use VSTS as a repository, though TFS can use Git. Maybe, I should look differently on this case. Does anyone know any possible solution?
You'll need tools to migrate between on-premise TFS and VSTS, like:
TFS Integration Tools
OpsHub Visual Studio Online Migration Utility
A useful blog for your reference.
I suspect that setting this up is going to be tricky or it's going to cost you.
The free OpsHub migration utility isn't going to help you in this scenario so you're looking at a commercial product like :
TaskTop Sync or OpsHub Integration Manager
but I haven't used them in this scenario so can't comment on either.
TFS Integration tools would probably do the job but you've got some work to do to get them working and it's not pretty. I have them setup at the minute to sync Work Items from TFS 2015 to VSTS for testing purposes and it works okay. My blog on setting them up with VSTS/2015 is here
Would you not consider doing your CI/CD directly from VSTS rather than an on-premise TFS? You could still have the build/release agent running on-prem and you could lock down permissions for your external devs so you control all the build and releases and any other projects.
Git would be a simpler way of merging code between VSTS and TFS2015 but that assumes you are using Git on your 2015 projects and I believe it would be manual process for someone to do this (someone may be able to comment on a way to make this work)
Related
Have an in house TFS server that employees use (using TFVC) and third-party contractors that are using VisualStudio Team Services (aka Visual Studio Online or VSO) (also using TFVC). Need to keep the two synced; projects in VSO get merges from check-ins from TFS and TFS get merges from VSO. The TFS instance has many dozen projects and the VSO instance has two or three of those in TFS.
Any suggestions appreciated.
While there are a few tools that can "sync" between different TFVC instances, it's very hard to keep the flow going and you often run into merge conflicts and other problems. The TFS Integration tools were an official solution from Microsoft, but those have been deprecated.
Given that you're on TFS 2017 and VSTS, I'd highly recommend switching to Git repositories. Git was made to handle scenarios like these, to have multiple hosts that need to share the history and from which you need to be able to sync sources across.
Both TFS 2017 and VSTS can host the repository for you and it's relatively easy to setup CI builds that sync the sources between branches on both instances to trigger pull requests.
I'm looking to upgrade our internal source control from the archaic TFS 2008 on prem, to the nice shiny VSTS (was Visual Studio Online) however it really doesn't simple a simple process. I tried using OpsHub but it looks like TFS 2010 is the earliest supported there.
I'd be happy just manually copying code but I don't know of a way to maintain branch relationships once those branches have been put in to VSTS.
Can anyone point me in the right direction for how to upgrade/move my code?
I'd be happy with an answer that explains how to maintain relationships when copying branches from one version to the other
You can try with this tool: TFS Integration Platform.
I have 2 different TFS repositories (one using Visual Studio Online and another using my own local on premise TFS instance) which I want to keep in sync using git-tfs. How do I need to set things up so that I can work locally in git and push changes up to both repositories? Please note both TFS repositories are using TFSVC.
As the main developer of git-tfs, believe me, that's not possible...
Git-tfs can only manage one TFVC repository.
Short answer: Not support.
If you want to sync Visual Studio Online and local TFS. You can use the TFS Integration Tools to setup a unidirectional sync, that should allow you to ensure that a TeamProject on your local TFS system remains in sync. However, they are complicated to setup and will be painfull to run. And There are commercial options that are ridiculously expensive, like OpsHub.
I'm planning a move from Jira to Team Foundation Server (TFS) 2015 and I can't find a good method of migrating the data between the two systems.
Are there any good methods out there ?
My company recently moved from Jira to TFS. I ended up writing my own utility to do the migration.
I've since published it as open source and it can be found on GitHub here:
https://github.com/KilskyreMan/JiraToTfs.git
The project will compile and run under Visual Studio 2015. It offers various mapping abilities via a GUI that should allow you (if needed) tailor your import.
Hope this helps - Ian.
For now, no documentation mentions how to migrate from Jira to TFS, but there are some plugins to have two-way sync between TFS and Jira, you can take a look at them:
TFS4JIRA (About About TFS4JIRA, you can get more information at https://confluence.spartez.com/display/TFS4JIRA/About+TFS4JIRA)
UseTFS
Atlassian Connector for Visual Studio
I have been using IBM Synergy tool in my earlier project for version control system.I like on of the feature which is auto propagation to child branches.
Now I am using TFS and hoping to get the same kind of feature here too but seems like its not available as could not find anything on the web on this.
I would really appreciate any help on this.
I don't believe a feature such as this exists in TFS at the moment (2013). However, there are some ALM tools that can help you propagate changes to associated branches, the 'Tfs Community Branch Tool extension'.
There are powershell modules that come with Team Foundation Power Tools you can likely cobble something together with as well, if the ALM tool doesn't work out for you. If you happen to be using TFS 2013 build you can inject a PowerShell script in your 'AfterBuild' phase to automate it, should that be something you care to do.
And as always, the TFS object model will provide you all the tools necessary to build out a TFS Build extension or MSBuild extension that would easily provide you with this functionality.