Can we migrate the whole CC VOB with all history to RTC?

Because of the power and flexibility of ClearCase (where an arbitrary
config spec can define an interesting/important configuration), it is
not logically possible to migrate "everything" in a CC VOB to any other
SCM system (including RTC).

So what is provided instead for ClearCase is a "synchronizer", that
allows you to migrate arbitrary configurations over from ClearCase to
RTC as you find that you need them.

We are currently working on additional material to guide your usage of
the synchronizer ... I should have something to post to jazz.net in a
few weeks.

Cheers,
Geoff

ghu wrote:

As to 2.0.0.2, RTC support importer to migrate whole SVN repository to
RTC. But it looks like the CC connector funtion does the migration
based on CC branch or stream, wheather users want one way or two way
sync between RTC and CC.

Is this the way it is? Can we have a way to do whole CC VOB migration
to RTC with all version hostory just like we do SVN to RTC? Has
anyone tried it?

Any tip is appreciated.

Because of the power and flexibility of ClearCase (where an arbitrary
config spec can define an interesting/important configuration), it is
not logically possible to migrate "everything" in a CC VOB to any other
SCM system (including RTC).

So what is provided instead for ClearCase is a "synchronizer", that
allows you to migrate arbitrary configurations over from ClearCase to
RTC as you find that you need them.

We are currently working on additional material to guide your usage of
the synchronizer ... I should have something to post to jazz.net in a
few weeks.

Cheers,
Geoff

Thanks, Geoff,
We have many VOBs with more than 20 branches to maintain (don't ask me why:)). So to create that many sync streams for each VOB doesn't seem to be practical. Plus that the bug tracking system we use is going to be converted from CQ to RTC for all teams, so patial convertion will break the link between changeset made on CC branches and the bug tracking on RTC. That is why I have been asked to see if we can do whole VOB convertion.

Waiting for your tips to come out to get us around this.

Hi Jim,

I'm now in the same building as you are, so let's just get together to
discuss (you can be a guinea pig for our new synchronizer guidance
document :-). We can then report our results/conclusions back to the forum.

Cheers,
Geoff


ghu wrote:

gmclemmwrote:
Because of the power and flexibility of ClearCase (where an arbitrary

config spec can define an interesting/important configuration), it
is
not logically possible to migrate "everything" in a CC VOB
to any other
SCM system (including RTC).

So what is provided instead for ClearCase is a
"synchronizer", that
allows you to migrate arbitrary configurations over from ClearCase
to
RTC as you find that you need them.

We are currently working on additional material to guide your usage
of
the synchronizer ... I should have something to post to jazz.net in
a
few weeks.

Cheers,
Geoff



Thanks, Geoff,
We have many VOBs with more than 20 branches to maintain (don't ask
me why:)). So to create that many sync streams for each VOB doesn't
seem to be practical. Plus that the bug tracking system we use is
going to be converted from CQ to RTC for all teams, so patial
convertion will break the link between changeset made on CC branches
and the bug tracking on RTC. That is why I have been asked to see if
we can do whole VOB convertion.

Waiting for your tips to come out to get us around this.

Hi Jim,

I'm now in the same building as you are, so let's just get together to
discuss (you can be a guinea pig for our new synchronizer guidance
document :-). We can then report our results/conclusions back to the forum.

Cheers,
Geoff

Hi, Geoff,
You guys moved in! Welcome!! I am at A1316C, 1st floor.

Yep, it is more convinient for me to bug you guys now:)

I, the guinea pig, has tested the Bugzilla importer we use for CQALM to RTC migration and the SVM2RTC importer. Now it is the CC importer.

Overall, it is a great product, I like it:)

Thanks,
Jim