importing code from Clearcase UCM to RTC
4 answers
Normally, I recommend that you only import "significant" baselines (e.g.
releases), and keep your ClearCase VOB's around in case you ever need to
go back to look up detailed history.
Cheers,
Geoff
On 9/30/2011 10:08 PM, rickcoup wrote:
releases), and keep your ClearCase VOB's around in case you ever need to
go back to look up detailed history.
Cheers,
Geoff
On 9/30/2011 10:08 PM, rickcoup wrote:
We are trying to put code from Clearcase UCM to RTC. It's a large
codebase with 10 year history in CC UCM. The snapshot of each version
is about 500MB.
Is it a good idea to import everything into RTC with importer or
synchronizer? Will the RTC perform better than UCM?
Thanks,
Rick
Is it a capacity concern or performance concern of the RTC. One of our VOB components is pretty big even with cutting history. Should we further de-component it?
Thanks,
Rick
Thanks,
Rick
Normally, I recommend that you only import "significant" baselines (e.g.
releases), and keep your ClearCase VOB's around in case you ever need to
go back to look up detailed history.
Cheers,
Geoff
RTC can handle large volumes of data in its repository, and versions are
stored in compressed and delta format, so it more that the RTC and
CC-UCM models are sufficiently different that you'll never get all the
information over from CC-UCM, so in case there is some obscure bit of
information you might want in the future, I'd recommend keeping the VOBs
around. And if you keep the VOBs around, then there is no reason to
load information other than the key baselines that represent important
information (like releases and active streams).
Cheers,
Geoff
On 10/1/2011 3:53 PM, rickcoup wrote:
stored in compressed and delta format, so it more that the RTC and
CC-UCM models are sufficiently different that you'll never get all the
information over from CC-UCM, so in case there is some obscure bit of
information you might want in the future, I'd recommend keeping the VOBs
around. And if you keep the VOBs around, then there is no reason to
load information other than the key baselines that represent important
information (like releases and active streams).
Cheers,
Geoff
On 10/1/2011 3:53 PM, rickcoup wrote:
Is it a capacity concern or performance concern of the RTC. One of our
VOB components is pretty big even with cutting history. Should we
further de-component it?
Thanks,
Rick
Normally, I recommend that you only import "significant"
baselines (e.g.
releases), and keep your ClearCase VOB's around in case you ever
need to
go back to look up detailed history.
Cheers,
Geoff
Is it a capacity concern or performance concern of the RTC. One of our VOB components is pretty big even with cutting history. Should we further de-component it?
Thanks,
Rick
RTC has a recommendation of total files and folders in one component not exceeding 50K.
I never wanted to migrate everything unless the client insist. I don't believe people want to see the code years ago.
Jirong