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 5
 [Expand]Big Picture/support/viewarticle/20018/
 [Expand]Server Administration/support/viewarticle/20087/
 [Expand]Web User's Guide/support/viewarticle/20071/
 [Expand]Clients/support/viewarticle/20077/
 [Collapse]Version Control Integration/support/viewarticle/20031/
  [Expand]AccuRev Integration/support/viewarticle/20025/
  [Expand]Borland StarTeam Integration/support/viewarticle/20233/
  [Expand]CVS Integration/support/viewarticle/20086/
  [Expand]Git Integration/support/viewarticle/20223/
  [Expand]IBM CMVC Integration/support/viewarticle/20222/
  [Expand]IBM Rational ClearCase Integration/support/viewarticle/20224/
  [Expand]IBM Rational Team Concert Integration/support/viewarticle/20164/
  [Expand]IBM Rational Synergy Integration/support/viewarticle/20238/
  [Expand]Mercurial Integration/support/viewarticle/20236/
  [Expand]Microsoft Team Foundation Server Integration/support/viewarticle/20085/
  [Expand]Microsoft Visual SourceSafe Integration/support/viewarticle/20160/
  [Expand]MKS Source Integrity Integration/support/viewarticle/20237/
  [Expand]Perforce Integration/support/viewarticle/20090/
  [Expand]SourceGear Vault Integration/support/viewarticle/20089/
  [Collapse]Subversion Integration/support/viewarticle/20088/
    Subversion Server Integration/support/viewarticle/20075/
   [Expand]GUI Client/support/viewarticle/20122/
   [Expand]Command Line Client/support/viewarticle/20157/
   [Collapse]Subversion Server Hooks/support/viewarticle/20209/
     ensure-review-started/support/viewarticle/20208/
     ensure-reviewed/support/viewarticle/20206/
     create-review/support/viewarticle/20179/
  [Expand]Surround SCM Integration/support/viewarticle/20318/
 [Expand]External Integrations/support/viewarticle/20301/
 [Expand]Techniques & Best Practices/support/viewarticle/20302/
 [Expand]Appendices/support/viewarticle/20078/
Updated: 4/18/2011 Applies To: CodeCollaborator 5 Rating: No votes Click to rate: PoorNot badAverageGoodExcellent

ccollab admin trigger ensure-review-started (for Subversion)

Top Previous Next

Usage: ccollab [global-options] admin trigger ensure-review-started [--ignore-integrate --review-id-regex <value>] <changelist-id>

ensure-review-started - Changelist cannot be submitted until review of this changelist exists

Command Options

Option

Required?

Description

--ignore-integrate

N

Allow integration changes to proceed without review

--review-id-regex <value>

N

Regular Expression that identifies Review ID in commit comment

<changelist-id>

Y

Changelist ID

This trigger ensures that a Review has been started before changes can be committed to version control.

If a Review has not been started, the commit will fail and the user will get an error message explaining that the changes need to be reviewed before commit.

To install this trigger you will need to create a pre-commit hook. If you already have a pre-commit hook, you can add our tool wherever it is appropriate; otherwise you will need to create an executable hook as described in the Subversion documentation (typically a batch file under Windows or a shell script under Linux/Mac).

Example Windows batch file:

"C:\Program Files\Code Collaborator Client\ccollab.exe" --url <collabUrl> --user <collabUser> --password <collabPasswd> --scm subversion --svn-repo-path %1 --svn-look-exe "C:\Program Files\Subversion\bin\svnlook.exe" admin trigger ensure-review-started --review-id-regex "review:\s+(\d+)" %2 || exit 1

Example Linux/OSX shell script:

/collab/install/ccollab --url <collabUrl> --user <collabUser> --password <collabPasswd> --scm subversion --svn-repo-path %1 --svn-look-exe /usr/bin/svnlook admin trigger ensure-review-started --review-id-regex "review:\s+(\d+)" $2 || exit 1

Note our use of "exit 1" to ensure that the script terminates with a non-zero exit code if our trigger application fails.

You must specify the --svn-repo-path and --svn-look-exe global options.

You must require developers to put the review ID somewhere in the Subversion commit message. The format of this text is completely up to you; you must supply a Java-style regular expression that identifies this text and specifically calls out the review ID inside that text using the --review-id-regex command option.



© 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