TFS to Azure DevOps Migration












0















I am undergoing the process of going from a very old TFS to Azure DevOps. There is a consideration whether to use TFVC or GIT. I used the git tfs deep clone feature to create a repo and it was about 3 GB. Does that mean the repo is too large to use as a git repo? If I cannot logically break it into smaller repos, does this mean I have to continue using TFVC instead?










share|improve this question





























    0















    I am undergoing the process of going from a very old TFS to Azure DevOps. There is a consideration whether to use TFVC or GIT. I used the git tfs deep clone feature to create a repo and it was about 3 GB. Does that mean the repo is too large to use as a git repo? If I cannot logically break it into smaller repos, does this mean I have to continue using TFVC instead?










    share|improve this question



























      0












      0








      0


      1






      I am undergoing the process of going from a very old TFS to Azure DevOps. There is a consideration whether to use TFVC or GIT. I used the git tfs deep clone feature to create a repo and it was about 3 GB. Does that mean the repo is too large to use as a git repo? If I cannot logically break it into smaller repos, does this mean I have to continue using TFVC instead?










      share|improve this question
















      I am undergoing the process of going from a very old TFS to Azure DevOps. There is a consideration whether to use TFVC or GIT. I used the git tfs deep clone feature to create a repo and it was about 3 GB. Does that mean the repo is too large to use as a git repo? If I cannot logically break it into smaller repos, does this mean I have to continue using TFVC instead?







      git visual-studio tfs azure-devops tfvc






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 22:21







      Ctznkane525

















      asked Nov 14 '18 at 22:08









      Ctznkane525Ctznkane525

      5,90321033




      5,90321033
























          1 Answer
          1






          active

          oldest

          votes


















          2















          does this mean I have to continue using TFVC instead?




          Not necessarily, you have a few options:




          • use Git LFS on your Azure server, as detailed by Microsoft in "Manage and store large files in Git"

          • use an intermediate server with VFS for Git active, which would then allow you to work with Git repos of multiple hundreds of GB(!).






          share|improve this answer
























          • An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

            – Edward Thomson
            Nov 15 '18 at 8:42











          • @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

            – VonC
            Nov 15 '18 at 8:50











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309468%2ftfs-to-azure-devops-migration%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2















          does this mean I have to continue using TFVC instead?




          Not necessarily, you have a few options:




          • use Git LFS on your Azure server, as detailed by Microsoft in "Manage and store large files in Git"

          • use an intermediate server with VFS for Git active, which would then allow you to work with Git repos of multiple hundreds of GB(!).






          share|improve this answer
























          • An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

            – Edward Thomson
            Nov 15 '18 at 8:42











          • @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

            – VonC
            Nov 15 '18 at 8:50
















          2















          does this mean I have to continue using TFVC instead?




          Not necessarily, you have a few options:




          • use Git LFS on your Azure server, as detailed by Microsoft in "Manage and store large files in Git"

          • use an intermediate server with VFS for Git active, which would then allow you to work with Git repos of multiple hundreds of GB(!).






          share|improve this answer
























          • An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

            – Edward Thomson
            Nov 15 '18 at 8:42











          • @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

            – VonC
            Nov 15 '18 at 8:50














          2












          2








          2








          does this mean I have to continue using TFVC instead?




          Not necessarily, you have a few options:




          • use Git LFS on your Azure server, as detailed by Microsoft in "Manage and store large files in Git"

          • use an intermediate server with VFS for Git active, which would then allow you to work with Git repos of multiple hundreds of GB(!).






          share|improve this answer














          does this mean I have to continue using TFVC instead?




          Not necessarily, you have a few options:




          • use Git LFS on your Azure server, as detailed by Microsoft in "Manage and store large files in Git"

          • use an intermediate server with VFS for Git active, which would then allow you to work with Git repos of multiple hundreds of GB(!).







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 6:03









          VonCVonC

          843k29426713223




          843k29426713223













          • An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

            – Edward Thomson
            Nov 15 '18 at 8:42











          • @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

            – VonC
            Nov 15 '18 at 8:50



















          • An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

            – Edward Thomson
            Nov 15 '18 at 8:42











          • @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

            – VonC
            Nov 15 '18 at 8:50

















          An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

          – Edward Thomson
          Nov 15 '18 at 8:42





          An in fact git itself without any modifications may be just fine here. My repository (the Azure DevOps repo) is about 3 GB and we're reasonably happy with it without VFS for Git.

          – Edward Thomson
          Nov 15 '18 at 8:42













          @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

          – VonC
          Nov 15 '18 at 8:50





          @EdwardThomson That means... a git status (mentioned in gvfs.io) is not too long? By the way, didn't you say in a recent podcast you had to change www.gvfs.io? (to something like vfs4g.io)

          – VonC
          Nov 15 '18 at 8:50




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309468%2ftfs-to-azure-devops-migration%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Bressuire

          Vorschmack

          Quarantine