Commands

The Command-Line Client provides a few basic commands which are unrelated to uploading files to the Collaborator Server:

• help – Display help on using the Command-Line Client
• login – Verify and/or change connection to the Collaborator Server
• info – Validates server connection and SCM configuration
• set – Save a global option setting

The primary function of the Command-Line Client is to upload review materials (files) to the Collaborator Server.

The recommended commands to use vary by Version Control System:

• AccuRev Commands
• ClearCase Commands
• CVS Commands
• Git Commands
• Mercurial Commands
• PTC Integrity Commands
• Perforce Commands
• Rational Synergy Commands
• Subversion Commands
• Team Foundation Commands

In addition to the Version Control specific commands, the Command-Line Client provides a few basic upload commands that work for any (or no) Version Control system:

• addfiles – Upload local files without diffs
• addchanges – Upload locally modified files controlled by an SCM
• adddiffs – Upload local or arbitrary diffs (see Uploading Diffs)
• addsimulinkarchives – Uploads Simulink model archive (see Reviewing Simulink Models)

Upload commands that deal with files managed by Version Control systems should be called from any sub-folder within the working copy of your repository (the place on your local machine where files from an SCM system are checked-out). Otherwise, the commands may fail to detect the SCM configuration.

The Command-Line Client also includes many commands meant for constructing custom scripts, usually used for integrating with external systems or implementing custom behaviors. For more information see Scripting: Overview.