More Information

Follow Us

Join our community of like minded
individuals and be the first to hear
about products, news and deals.

Newsletter



[Collapse]CodeCollaborator 6
 [Expand]Big Picture/support/viewarticle/20412/
 [Expand]Server Administration/support/viewarticle/20483/
 [Expand]Web User's Guide/support/viewarticle/20467/
 [Expand]Clients/support/viewarticle/20473/
 [Collapse]Version Control Integration/support/viewarticle/20425/
  [Expand]AccuRev Integration/support/viewarticle/20419/
  [Expand]Borland StarTeam Integration/support/viewarticle/20681/
  [Expand]CVS Integration/support/viewarticle/20482/
  [Expand]Git Integration/support/viewarticle/20494/
  [Expand]IBM CMVC Integration/support/viewarticle/20556/
  [Expand]IBM Rational ClearCase Integration/support/viewarticle/20530/
  [Expand]IBM Rational Synergy Integration/support/viewarticle/20528/
  [Expand]IBM Rational Team Concert Integration/support/viewarticle/20552/
  [Expand]Mercurial Integration/support/viewarticle/20491/
  [Expand]Microsoft Team Foundation Server Integration/support/viewarticle/20481/
  [Expand]Microsoft Visual SourceSafe Integration/support/viewarticle/20620/
  [Expand]MKS Source Integrity Integration/support/viewarticle/20500/
  [Collapse]Perforce Integration/support/viewarticle/20486/
    Perforce Server Integration/support/viewarticle/20472/
   [Expand]GUI Client/support/viewarticle/20489/
   [Expand]Command Line Client/support/viewarticle/20513/
    P4V / P4Win Integration/support/viewarticle/20492/
   [Expand]Perforce Server Triggers/support/viewarticle/20470/
  [Expand]SourceGear Vault Integration/support/viewarticle/20485/
  [Expand]Subversion Integration/support/viewarticle/20484/
  [Expand]Surround SCM Integration/support/viewarticle/20549/
 [Expand]External Integrations/support/viewarticle/20740/
 [Expand]Techniques & Best Practices/support/viewarticle/20741/
 [Expand]Appendices/support/viewarticle/20474/
Updated: 12/21/2011 Applies To: CodeCollaborator 6 Rating: No votes Click to rate: PoorNot badAverageGoodExcellent

Command Line Client

Top Previous Next

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 CodeCollaborator server

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

The addchangelist command will upload Perforce changelists into CodeCollaborator. 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

Option

Description

--p4 <value>

Full path to the P4 executable

--p4port <value>

How to connect to the Perforce server

--p4user <value>

Perforce user name

--p4passwd <value>

Perforce password or ticket

--p4client <value>

Mapping of Perforce server data to the local machine

--p4-ignore-integration-history <value>

Ignore integration history when calculating predecessor

--p4charset <value>

Perforce character set used for translation of Unicode files

--p4-require-empty-default-changelist

If true, don't allow uploads if the default changelist contains files

--p4-specify-command-charset <value>

Should a character set be specified for communication with Perforce

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



© 2012 SmartBear Software. All rights reserved.
Email Send feedback on this document
 

+1 978-236-7900

© 2012 SmartBear Software. All rights reserved.
Home | Privacy | Terms of Use | About | Contact Us | Site Map | Print