Summary

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

Details

Page properties

Content

...	...	@@ -1,11 +1,11 @@
1	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	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.
3	3
4	4	The process to sync the tfvc to the git repo
5	5
6	6	1. pull all the latest changes from TFVC via cli
7		-
8		-1. {{code language="powershell"}}tf vc workspace /new migration /collection:https://dev.azure.com/ebsphere
	8	+\\{{code language="powershell"}}tf vc workspace /new migration /collection:https://dev.azure.com/ebsphere
9	9	mkdir c:\dev\src\migration
10	10	cd c:\dev\src\migration
11	11	tf vc get{{/code}}
...	...	@@ -12,12 +12,17 @@
12	12
13	13	1. do an extract and dump into excel to generate the copy commands
14	14	\\{{code language="PowerShell"}}forfiles /P C:\dev\src\migration /S /C "cmd /c echo @isdir;@ext;@path" >>list3.txt
15		-
16	16	{{/code}}
	16	+
17	17	1. execute copy commands from excel generation
18		-11. this will split the source into master and feature brances
	18	+11. this will split the source into master and feature branches
19	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	+
20	20	1. run the [[tf-sync.ps1>>doc:.tf-sync.WebHome]] script
21	21	11. this will parse the directories that was created into the migration repository
22	22	111. see [[mappings >>doc:.mappings.WebHome]]for structure
23		-11. this will create or update the migration repository
	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