Commands recommended for Perforce

ccollab addchangelist - Attaches an atomic changelist to a review

ccollab addp4diffs - Uploads diffs generated from p4 diff2 command

ccollab addversions - Attaches any 2 given versions to a review

ccollab commit - Commit changes in the review

ccollab addp4job - Adds all numbered local changes that fix a job to the review

ccollab admin syncusers - Synchronizes the Perforce user list with the Collaborator server

ccollab admin changelist update-id - Updates the changelist ID so Collaborator reflects the renumbered Perforce changelist ID

The addchangelist command will upload Perforce changelists into Collaborator. You can upload changelists either before or after they are submitted, but you cannot upload the default changelist.

Configuration

In most cases, the Command-Line Client can automatically detect your Perforce configuration. Try testing your configuration to verify the configuration is detected correctly.

If the Command-Line Client is unable to detect your Perforce configuration or you want to override the detected settings, you can manually specify Perforce settings using global options.

To manually configure the Command-Line Client to use Perforce, execute the following command:

ccollab set scm perforce

Perforce-specific Options

If your Perforce server requires ticket-based authentication (server security level 3) then the configured p4passwd will be used to automatically issue 'p4 login' and acquire a new ticket as necessary.

If you want to ignore the integration history of files when determining the previous version of the file and look only at the path you should set p4-ignore-integration-history to yes like so:

ccollab set p4-ignore-integration-history yes

Note for Windows users: Sometimes Perforce server uses Windows machine host name as a default name, ignoring the real Perforce client name. To avoid that issue, specify the needed Perforce client name directly in the Collaborator with the --p4client <name> command.