locked
Sync SVN repository to TFS integrated Git for CI/CD RRS feed

  • Question

  • We have a bunch of teams happily using the integrated TFS Git repo in TFS 2013 and set up with CI/CD, but we have one team that's been off on their own for a while - they've only been using TFS for Work Item tracking and have been using a local SVN repo with local builds, manual QA and deploy etc. We want to bring them into the fold for CI builds, automation and CD, however they don't want to transition to Git (don't see the point) and are adamant they want to use SVN.

    Because all of our other teams use Git our standard TFS Team Project templates are set up to use integrated Git, so we can't use something like SVNBridge to link their SVN repo to the TFS version control without having to go through a lengthy process of creating new team projects and then using TFS Integration to move all of the work items (and history) across - a messy proposition at best.

    What I'd like to do then is use something like SubGit to mirror the SVN repo into TFS integrated Git - but all of the SubGit documentation refers to a local Git repo which gets created as part of the SubGit config - I'd want it instead to use the already existing TFS integrated Git repo that relates to the existing Team Project. Git-svn looks like an option but with a lot of scripting and hooking to wrap it all in - additional maintenance/admin I really could do without.

    I'm open to any suggestions around the best way to attack this conundrum - given the team MUST use SVN and the CI/CD build system MUST be in TFS (preferably using integrated Git as the TFS repo) what's the best way to get sync and automated CI working?

    Wednesday, July 22, 2015 3:33 PM

Answers

  • Hi Mark,  

    Thanks for your reply.

    As far as I know there’s no a default way to do that. May be you need create a custom SVN service to achieve that, once a commit occurred in SVN, this commit event will trigger custom service to run a script to commit and push the repo to Git.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, July 23, 2015 9:37 AM
    Moderator

All replies

  • Hi Mark, 

    Thanks for your post.

    We suggest you move SVN source files to  that team’s TFS Git team project, then create CI builds in this team project like you did in other team projects.

    http://www.incyclesoftware.com/2013/08/how-easy-its-to-migrate-svn-to-tfs-2013-git-repo/

    http://www.incyclesoftware.com/2013/08/migrate-svn-to-tfs-its-free/


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, July 23, 2015 6:09 AM
    Moderator
  • As I stated in the original post - the team CANNOT move from SVN to Git, so I'm looking for a way of continuously synchronising the two repositories such that a commit in SVN causes a push to Git and kicks off a CI build. I'd LOVE to move them across to Git, but that seems to be highly unlikely in our internal political climate!
    Thursday, July 23, 2015 9:01 AM
  • Hi Mark,  

    Thanks for your reply.

    As far as I know there’s no a default way to do that. May be you need create a custom SVN service to achieve that, once a commit occurred in SVN, this commit event will trigger custom service to run a script to commit and push the repo to Git.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, July 23, 2015 9:37 AM
    Moderator