Forum Discussion
ebrown_1
14 years agoSmartBear Alumni (Retired)
Omri,
As you point out, the scenario of an SCM where there are no changelists and where code reviews are post-commit requires more work on the part of the review author, who must manually create the changelist. The addversions command was created for precisely this reason, and it was designed to take a list of files and versions as input. I apologize if how to do this wasn't clear from the documentation, but you can also run "ccollab --scm clearcase help addversions" to see the syntax and examples specific to ClearCase.
Here's an example input file:
hello.c /main/test/9 /main/3
world.c /main/test/5 /main/3
Then to create the review, pipe the contents to the addversions command:
ccollab addversions new < fileversionlist.txt
If there are more tasks you want to perform when creating the review, you can instead create a batch xml input file to create the review and then do additional tasks like adding materials, participants, start the review, etc. See the documentation or run "ccollab help admin batch" for more info.
Hope this helps,
Eric
Related Content
- 3 years ago
Recent Discussions
- 3 months ago