Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
72:subversion_migration [2018/07/09 16:55] – [Migration of Legacy SVN CMS Profile] bkkr72:subversion_migration [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 7: Line 7:
   - Configure your Subversion servers for CMS-Type Subversion in the CMS section of PKitConfig.xml.   - Configure your Subversion servers for CMS-Type Subversion in the CMS section of PKitConfig.xml.
   - Ensure no files are checked out in Stages for the legacy SVN profiles at the time of migration. To create a list of currently checked out SVN files execute the following commands on the Stages server in a shell with administrative permissions.   - Ensure no files are checked out in Stages for the legacy SVN profiles at the time of migration. To create a list of currently checked out SVN files execute the following commands on the Stages server in a shell with administrative permissions.
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font> +      - cd [STAGES_INSTALL_DIR]\stages 
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\listCheckouts.bat SVN</font>+      - bin\listCheckouts.bat SVN
  
 === Instructions === === Instructions ===
  
   - Before migrating all existing SVN CMS profiles to Subversion CMS profiles, please review all changes that will be done by the migration script. Therefore execute a dry run of the migration script on the Stages server in a shell with administrative permissions.   - Before migrating all existing SVN CMS profiles to Subversion CMS profiles, please review all changes that will be done by the migration script. Therefore execute a dry run of the migration script on the Stages server in a shell with administrative permissions.
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font> +      - cd [STAGES_INSTALL_DIR]\stages 
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\migrateSubversion.bat system show > migration.log 2>&1</font>+      - bin\migrateSubversion.bat system show > migration.log 2>&1
   - If the migration dry run was successful, please execute the following commands to actually do the migration.   - If the migration dry run was successful, please execute the following commands to actually do the migration.
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font> +      - cd [STAGES_INSTALL_DIR]\stages 
-      - <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\migrateSubversion.bat system write > migration.log 2>&1</font>+      - bin\migrateSubversion.bat system write > migration.log 2>&1 
 + 
 +===  Recommended 'Clean-Up' Steps  === 
 + 
 +When all legacy SVN CM profiles are migrated the following clean up steps are recommended: 
 + 
 +1. Delete the local SVN sandboxes on the Stages server as they are no longer needed. The file system location is defined in PKitConfig.xml in element 
 + 
 +<code> 
 +<cms-type name=”SVN” ...> 
 + ... 
 + <cms-property name="sandboxDirectory" value="[DIRECTORY_PATH]"/> 
 + ... 
 +</cms-type> 
 +</code> 
 + 
 +2. To prevent Stages users from creating legacy SVN CMS profiles, please delete the configuration for the legacy SVN interface in PKitConfig.xml. Delete the 
 + 
 +<code> 
 +<cms-type name=”SVN” ...> 
 + ... 
 +</cms-type> 
 +</code> 
 + 
 +3. Restart Stages for the configuration changes take effect.