|
Archiving Reviews |
|
Collaborator can pack reviews to an external Zip archive. You can use this feature to keep historical records of the reviews (for instance, because of regulatory requirements), or to export review information to a non-proprietary format. Note: This feature is only supported in Collaborator Enterprise. For a complete list of differences between Collaborator editions, please see the comparison page. Creating Archives There are two ways to archive reviews: from the Web Client and from the command-line. To archive a review from the command-line call the ccollab admin archive command. See command description for its syntax and examples. To archive a review from within the Web UI:
This will invoke a standard Save As dialog where you can specify the location for the archive. Creating Archives Automatically You may use Collaborator server triggers to archive reviews automatically. The general idea is to install the Command-Line Client on a server machine and call the ccollab admin archive command via the server's phase change trigger. Below are the detailed steps of how to achieve this:
You nay need to change paths to the Collaborator command line client and to the archives folder as necessary. Note: In the example above the trigger does not check if the phase has transitioned to completed, cancelled or rejected. Since the ccollab admin archive command ignores in-progress reviews (by default) you can simply call it on every phase changed event. If your team is using the tool heavily, then you should create a shell script or batch file, and check the review phase before calling the ccollab admin archive command. This will result in improved performance, but is not really necessary for small or medium sized installations.
The Archive Contents For each review a separate archive is created. Generated files have the names in the format "review-ID-archive.zip", where ID stands for the identifier of the review. Each archive contains the following information about the review:
The naming structure of subfolders that store review materials, depends on how the materials were uploaded. For changes uploaded via version control system, the folder name will contain the name of SCM, the name of the repository and (if available) the ID of the changeset ("git-git.example.com_foo_repo.git-85d2f5ccb7f27e1628c09e4d1373f"). For uploads of arbitrary files, the folder names will contain the "upload-file-" portion followed by the date and time ("upload-file-2015-08-18-02-58-59").
|
|
© 2003-2025 SmartBear Software. All rights reserved. |