Differences

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

--- 72:subversion_migration [2018/07/09 16:33] – created bkkr
+++ 72:subversion_migration [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 9: / Line 9: @@
       - cd [STAGES_INSTALL_DIR]\stages
       - bin\listCheckouts.bat SVN
+=== 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.
+      - cd [STAGES_INSTALL_DIR]\stages
+      - 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.
+      - cd [STAGES_INSTALL_DIR]\stages
+      - 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:
+. 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>
+. 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>
+. Restart Stages for the configuration changes take effect.