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/
  [Collapse]IBM Rational ClearCase Integration/support/viewarticle/20530/
    GUI Client/support/viewarticle/20586/
   [Collapse]Command Line Client/support/viewarticle/20612/
     addchanges (for ClearCase)/support/viewarticle/20506/
     addchangelist (for ClearCase)/support/viewarticle/20588/
     addversions (for ClearCase)/support/viewarticle/20596/
     addactivity/support/viewarticle/20537/
     commit (for ClearCase)/support/viewarticle/20672/
  [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/
  [Expand]Perforce Integration/support/viewarticle/20486/
  [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

ccollab addversions (for ClearCase)

Top Previous Next

Usage: ccollab [global-options] addversions [--upload-comment <value> --version-spec <value> [<value> ...]] <review> [<file-path>] [<version>] [<predecessor-version>]

addversions - Attaches any 2 given versions to a review

Command Options

Option

Required?

Description

--upload-comment <value>

N

Comment used to upload files (default is "Local changes")

--version-spec <value> [<value> ...]

N

A version to be reviewed can be specified by a version-spec. A version-spec is given by <path> <version> [<previous-version>], where <path> is the filename or server path of the file, <version> is the version to be reviewed, and <previous-version> is an optional version that <version> should be diff'ed against. Each argument must be quoted if any embedded spaces exist in an argument. Typically a version-spec is not used on the commandline. Instead, specify the parts using the <file-path>, <version> and optionally the <predecessor-version> arguments

<review>

Y

Must be either an integer review-id, 'new', 'ask', or 'last'

<file-path>

N

Path of the file whose versions are to be added to the review. Requires a value for <version>

<version>

N

Version of the file to be added to the review. Required if <file-path> is given

<predecessor-version>

N

Predecessor version to be added to the review

Uploads specific versions of a file or files to a review. A version-spec

is given by a file path followed by a version, and optionally, a predecessor

version:

file-path version [predecessor-version]

If no predecessor version is explicity given, diffs will be generated using

the predecessor version as determined from the SCM system.

Adding versions for a single file can be done with command line arguments

given after the review number. To upload versions for multiple files, the

file and versions may be submitted on lines read from standard input. If

the path and versions are not given on the command line, the client will

expect to read them from stdin. Each line read should be in the format shown

for the version-spec option. Some example command lines for reading versions

from stdin:

ccollab addversions 86753

ccollab addversions last < versionlist.txt

cat versionlist.txt | ccollab addversions new

When supplying the version list on the command line or in an input file, the

keyword 'local' can be used to denote the version corresponding to the local

version of the file. The 'local' keyword can only be used for the first

version argument, not the predecessor version.

Examples of specifying versions on the command line for ClearCase:

ccollab addversions new hello.c \main\mydev\6 \main\8

ccollab addversions last Main.java /main/dev/31

To compare the local version of the ClearCase file to a previous version in

an edit list or input list, use 'local' as the initial version. If the file

is checked out as '/main/CHECKEDOUT', then 'local' is equivalent to using

'/main/CHECKEDOUT' as the initial version. Otherwise 'local' would refer to

the latest version of the file. For example, if the local file hello.c is

at version '/main/9' and has predecessor '/main/8' then all of the following

lines would be equivalent:

hello.c /main/9

hello.c local

hello.c /main/9 /main/8

hello.c local /main/8

You can also reference a LATEST version, e.g.:

ccollab addversions new hello.c \main\ga_1.0\6 \main\LATEST

To upload a version with no predecessor version, use '\main\0':

ccollab addversions new hello.c \main\ga_1.0\6 \main\0



© 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