Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,28 +1,0 @@
1		-We will migrate all the tfvc repos into one git repository called "migration" as a staging area to facilitate the process of moving the individual solutions into its final git location. This can be done in a delta fasion until we restrict the tfvc repos and everyone starts working off the git staging repo.
2		-
3		-Feature branches can be merged back into master via a pull request and the feature branches that are not applicable anymore can be abandoned.
4		-
5		-The process to sync the tfvc to the git repo
6		-
7		-1. pull all the latest changes from TFVC via cli
8		-\\{{code language="powershell"}}tf vc workspace /new migration /collection:https://dev.azure.com/ebsphere
9		-mkdir c:\dev\src\migration
10		-cd c:\dev\src\migration
11		-tf vc get{{/code}}
12		-
13		-1. do an extract and dump into excel to generate the copy commands
14		-\\{{code language="PowerShell"}}forfiles /P C:\dev\src\migration /S /C "cmd /c echo @isdir;@ext;@path" >>list3.txt{{/code}}
15		-
16		-(% start="3" %)
17		-1. execute copy commands from excel generation
18		-11. this will split the source into master and feature branches
19		-
20		-1. A recon step must be performed at this stage to make sure all files where copied this is performed in excel
21		-11. get directory listing of copied files (dir/s/b %path% > list.txt) and dump into "recon" sheet and "recon" column in main sheet will indicate if any are missing with a 1
22		-11. rectify any problematic items
23		-
24		-1. run the [[tf-sync.ps1>>doc:.tf-sync.WebHome]] script
25		-11. this will parse the directories that was created into the migration repository
26		-111. see [[mappings >>doc:.mappings.WebHome]]for structure
27		-11. this will create or update the migration repository in GIT
28		-11. an .gitignore gets injected this will make sure binaries are excluded