It's all about the answers!

Ask a question

Config for nightly CC=>RTC sync


bill compton (63) | asked Aug 11 '10, 5:01 p.m.
We plan to "mirror" the main/latest branch in a large CC repo into RTC. As part of this, we plan to create a CC "SYNC" branch off of main so that while the sync is running we don't lock up CC main. We want CC SYNC to be (effectively) always an exact copy of CC main/latest so that the mirror in RTC is therefore also a copy of CC main/latest.

The question is: how do we automatically keep CC SYNC current with CC main/latest? Is there some sort of ct command to apply all changes from one CC branch to another that would do this?

Thanks!

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 11 '10, 9:34 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This is really a ClearCase question, so best asked at:
http://www.ibm.com/developerworks/forums/forum.jspa?forumID=333
where all the ClearCase experts hang out (:-), but this is an easy one:
in a view that whose config spec is looking at SYNC/latest, execute a
findmerge command like:

cleartool findmerge -avobs -fversion /main

Your ClearCase admins will all know how to do this, but if you're doing
this yourself, you'll want to read the "findmerge" entry in the
clearcase command reference manual ("cleartool man findmerge" will open
that page in your web browser).

Cheers,
Geoff

On 8/11/2010 5:07 PM, billcompton wrote:
We plan to "mirror" the main/latest branch in a large CC
repo into RTC. As part of this, we plan to create a CC
"SYNC" branch off of main so that while the sync is running
we don't lock up CC main. We want CC SYNC to be (effectively) always
an exact copy of CC main/latest so that the mirror in RTC is
therefore also a copy of CC main/latest.

The question is: how do we automatically keep CC SYNC current with CC
main/latest? Is there some sort of ct command to apply all changes
from one CC branch to another that would do this?

Thanks!

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.