Wiki source code of tfvc
Last modified by Rudi Marais on 2023/05/22 23:50
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = Overview = | ||
| 2 | |||
| 3 | |||
| 4 | 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. | ||
| 5 | |||
| 6 | Feature branches can be merged back into master via a pull request and the feature branches that are not applicable anymore can be abandoned. | ||
| 7 | |||
| 8 | = Migration process = | ||
| 9 | |||
| 10 | |||
| 11 | The process to sync the tfvc to the git repo | ||
| 12 | |||
| 13 | 1. pull all the latest changes from TFVC via cli | ||
| 14 | \\{{code language="powershell"}}tf vc workspace /new migration /collection:https://dev.azure.com/ebsphere | ||
| 15 | mkdir c:\dev\src\migration | ||
| 16 | cd c:\dev\src\migration | ||
| 17 | tf vc get{{/code}} | ||
| 18 | |||
| 19 | 1. do an extract and dump into excel to generate the copy commands | ||
| 20 | \\{{code language="PowerShell"}}forfiles /P C:\dev\src\migration /S /C "cmd /c echo @isdir;@ext;@path" >>list3.txt{{/code}} | ||
| 21 | |||
| 22 | 1. execute copy commands from excel generation | ||
| 23 | 11. this will split the source into master and feature branches | ||
| 24 | |||
| 25 | 1. A recon step must be performed at this stage to make sure all files where copied this is performed in excel | ||
| 26 | 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 | ||
| 27 | 11. rectify any problematic items | ||
| 28 | |||
| 29 | 1. run the [[tf-sync.ps1>>doc:technical-documentation.Source Control.migration.tfvc.tf-sync.WebHome]] script | ||
| 30 | 11. this will parse the directories that was created into the migration repository | ||
| 31 | 111. see [[mappings >>doc:technical-documentation.Source Control.migration.tfvc.mappings.WebHome]]for structure | ||
| 32 | 11. this will create or update the migration repository in GIT | ||
| 33 | 11. an .gitignore gets injected this will make sure binaries are excluded | ||
| 34 | 11. subsequent runs if the repo already exists will create a feature branch for the main branches timestamped with the date is was ran | ||
| 35 | ie: /feature/master-20220202-172700 | ||
| 36 | |||
| 37 | = Disable TFVC repository = | ||
| 38 | |||
| 39 | After a repository has been moved to the staging environment and a call has been made to switch off the old repository we will put the old repository in read-only mode, the steps are: | ||
| 40 | |||
| 41 | 1. Notify the team and request that any pending changes need to be committed | ||
| 42 | 1. Do a final delta migration of the repository | ||
| 43 | 1. Disable inheritance on the repository | ||
| 44 | 1. Remove Contributors group | ||
| 45 | 1. Make sure the Readers group is present | ||
| 46 | |||
| 47 |