Running P4Convert

Import Mode

Import Mode will pull in file revisions from a Subversion dump file or CVS repository, adding them to the Perforce Server specified by the connection details in the configuration options. To use this mode set: 

com.p4convert.p4.mode=IMPORT

Care should be taken when adding data to a pre-existing Perforce Server that the revision actions do not conflict with revisions already in the Perforce Server; typically, this can occur if the Server has been in-use since the previous migration.

To avoid such scenarios the import should either be to a unique depot, to avoid conflict, or the Perforce Server should be Read Only during subsequent migrations. After a conversion is complete, it is possible to merge the new data with an existing depot using tools like PerfMerge++.

The converter will check that your Perforce Server has no pending changes, and will abort a conversion if any are detected.

Configuration options specific to Import Mode

  1. Perforce server address and port (escape the ':' with '\:'): 

    com.p4convert.p4.port=localhost\:4444

  2. Default user and client for server connection: 

    com.p4convert.p4.client=p4-client
com.p4convert.p4.user=p4-user

  3. Client workspace root used to import files into Perforce: 

    com.p4convert.p4.clientRoot=/Users/bruno/ws/

  4. If Security is set to level 1 or greater, then the p4-user must have admin permissions in the Protection table and the password supplied as a string (the default is set to ws/ under your local directory): 

    com.p4convert.p4.passwd=PaSSwoRd

  5. Alternatively if the user is already logged in and there is a valid ticket, then leave the password field unset and set your environment for P4TICKETS (don't rely on the P4TICKETS unset default as p4-java will not find your ticket file).

Warning

For long running conversions where authentication is required, please insure that the conversion user has an "Unlimited" login timeout.