This is an old revision of the document!


Subversion Integration

Migration of Legacy SVN CMS Profile

Prerequisites

  1. Configure your Subversion servers for CMS-Type Subversion in the CMS section of PKitConfig.xml.
  2. 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.
    1. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font>
    2. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\listCheckouts.bat SVN</font>

Instructions

  1. 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.
    1. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font>
    2. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\migrateSubversion.bat system show > migration.log 2>&1</font>
  2. If the migration dry run was successful, please execute the following commands to actually do the migration.
    1. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>cd [STAGES_INSTALL_DIR]\stages</font>
    2. <font inherit/Courier New,Courier,monospace;;inherit;;inherit>bin\migrateSubversion.bat system write > migration.log 2>&1</font>