As the old vsts source code archive server is about to prepare the code are still in use on the server need to migrate all the old to the new vsts server.
So we need to migrate all of the code needed to subsequent use of the new vsts above. Although only a migration code, but it comes to specifics
Really a lot, the first thing you need to migrate a list of code, followed by the code to figure out the various versions of the current situation, if someone else is editing, whether the recent
There are big release, or have projects underway.
First, under the code you need to migrate directory records in a list down the list, followed by review this inventory list to see if there are any omissions or
Code which does not need, after the completion of the audit the finalized migration of the range.
Then it is to choose the right time to migrate, because many projects in parallel, but also requires a lot of code after the merger in the near future on the line, so I follow
Case of some large releases of code branches and merging situations.
Then there is good coordination with the developers time to migrate, because migration, to ensure that the migration of the code has been checked in to the server, and then I get the most
After the new code migration to the new server.
The final step is also the most important, if the last time the migration, find someone still change the code, the code does not have a lot of check-in, then it means that migration is not
The latest code, you need to re-migrate. So everything is in place, only the East, the East is very important ah.
After last week's final release is complete, the confirmation code they have already checked in, and get the latest code to complete the migration, and then let us get the latest
Code confirmation, everything is OK, finally completed this month duration of the work.
Reproduced in: https: //www.cnblogs.com/kevinGao/p/4188736.html