We are migrating 60 Thousand workitems from TFS 2010 environment to 2012 environment using the TFS Integration tool. In the test environment is took very less time as less traffic was there , but in production environment it is taking more than 2 weeks as calculated by the current speed it is going in.
Is there anything we can do to speed up the migration ?
How does the tool works to migrate these workitems ?
You can add new query in TFS Integration Tool to reduce the amount of work items to be migrated at one time.
Related
According to Microsoft's migration guide (p. 25), the TFSMigrator tool that will migrate data to DevOps only supports the current version and 1 previous version of TFS which means migrating to the newest TFS version is integral in the process.
I'm using an old version of TFS which I wouldn't have too big an issue upgrading except the server it runs on is Windows Server 2008 which doesn't support anything past TFS 2012.
Since all I need is the code repository as it sits today (I don't care about work items, history, or anything else), is there an alternative method for migrating my code?
I'm okay with something semi-manual if necessary. I have about 30 projects to migrate so if I had to migrate project by project, that isn't a big deal. I'm just hoping not to have to recreate each project by hand.
Try git-tfs.
The process is:
Use git-tfs to turn the source TFVC repo into a local Git repo with all of the history preserved
Use git-tfs to "check in" the Git repo to the target TFVC repo
A few caveats:
It's going to be slow.
It's not going to be a full-fidelity migration; you're going to lose the dates of the checkins and possibly the identity of the person who made the checkin in the target system.
An alternative is to spin up a non-production modern TFS environment, clone your team project collection, upgrade it on the non-prod instance, then use the migration tool. That's going to capture everything with full fidelity, and that official tool is the only option you have if you want full fidelity.
We have a 50GB on-premises TFS collection, which we want to have migrated to TFS online. We are now using the OpsHub Visual Studio Online Migration Utility, to test with. The conversion of some separate test projects seem to work fine, so now we are trying to measure the time it will take for a full migration. It looks like the migration of all 78K changesets will take about a month. That is way too long for us. The tool is using only one Core of our 8 available Cores. I don't see other resource bottlenecks, other than the CPU (the Core in use is over 50% most of the time).
Are there any tips for a faster migration? Is there any way to speed up things?
Besides asking you all for a possible solution, I am now also trying to do several smaller migrations in parallel. As soon as I have results of that, I will share them.
Which version you are using?
There is performance issue with label which is fixed in version 1.0.1.005.
If your projects are independent in commit (Branch and Merge operation) then you can create migration, project wise which run parallel.
In TFS2008, is there anyone to tell the Warehouse Controller job to do a full rebuild of the Analysis Services Cube everytime? I know this can be done in TFS 2010 but I can't seem to find any information regarding this for TFS 2008.
If not then would it be a bad idea for me to schedule in a task to manual rebuild the cube just before the warehouse job runs every 5 hours or so ?
we have a very tricky situation which am sure can be avoided if dealt with properly.
There were 5 different branches of a specific application in our TFS 2010. All the branches were merged into 1 branch and since the merging was done by a system administrator who wasn't part of the development team, we ended up cleaning the code (adding the missed changes from 3 separate places where ever they were conflicts) This amounted to almost 2 weeks of extra effort to get the code branch stabilised and tested before proceeding further.
What should be the best practice to be followed to avoid such frustrations in future as we have multiple code branches for different development projects running on same applications.
See the Visual Studio ALM Rangers Team Foundation Server 2010 Branching Guide.
I have a lot of legacy Delphi 5 & 6 Code. We want to test this code using the new Microsoft Test Manager (part of VS2010)
To effectively track your testing using this tool you need to use build numbers. To get Delphi 5 or 6 building in TFS Build 2010 is a huge task. One that I am not sure I want to take on.
Is there a way I can just insert my build numbers in to tfs?
Build numbers are stored in a global list which the build process adds to each time it runs. You can download the global list from TFS, edit it and then republish the updated version back up to the server.
I'd suggest using the TFS 2010 Power Tools to do it (link)