Differences

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

Link to this comparison view

Both sides previous revision Previous revision
72:subversion_migration [2018/07/09 16:55]
bkkr [Migration of Legacy SVN CMS Profile]
72:subversion_migration [2018/07/09 16:57] (current)
bkkr [Migration of Legacy SVN CMS Profile]
Line 18: Line 18:
       - <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​cd [STAGES_INSTALL_DIR]\stages</​font>​       - <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​cd [STAGES_INSTALL_DIR]\stages</​font>​
       - <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​bin\migrateSubversion.bat system write > migration.log 2>&​1</​font>​       - <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​bin\migrateSubversion.bat system write > migration.log 2>&​1</​font>​
 +
 +===  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.