Team Concert v4.0 - compare baselines using the 'scm' command-line utility
![]()
p m n (27●1●9●13)
| asked Nov 18 '13, 11:39 p.m.
retagged Dec 16 '13, 5:45 p.m. by David Lafreniere (4.8k●7)
I need some guidance with running the "scm compare" command:
I'm trying to compare the latest in a stream ('my_test_stream') and a baseline (Release_2013_1); however, I get the following error.
/home/pmn/workspaces/pmn_release_2013_1 > scm compare -r local -c nm -I f stream my_test_stream baseline Release_2013_1
I suspect the command syntax is correct; though, I'm unable to find out what the colliding item is. Is there a way to find out where this collision is occurring? Or to qualify the above command to specifically use 1016 instead of 1098?
Here's the output of the status of the workspace (just to show you that there is no duplication in the components):
/home/pmn/workspaces/pmn_release_2013_1 > scm status -w
I'm running this from an RHEL host and I'm connected to RTC version 4.0.
Regards...
|