What are the advantages & disadvantages of using Rational ClearCase Bridge versus Rational ClearCase Version Importer?
Robert Gormally (6●1●1)
| asked Jun 04 '14, 5:47 a.m.
retagged Jun 04 '14, 9:00 a.m. by Masabumi koinuma (461●1●5)
Our team is currently utilising ClearCase UCM for source control on a large project, and we are in the process of migrating to RTC for project lifecycle management.
We are trying to determine whether to migrate our (large) codebase from our existing UCM repository into RTC using ClearCase Version Importer, or to integrate with it using ClearCase Bridge. What are the advantages & disadvantages of using Rational ClearCase Bridge versus Rational ClearCase Version Importer? If we decide to use a Bridge, what functionality/features of RTC will not be available to us? Thanks for your help! |
2 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 04 '14, 8:15 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jun 04 '14, 10:01 p.m.
With the ClearCase Bridge, you are continuing to use ClearCase for versioning, and are using RTC for change request management, task management, and planning. With the ClearCase importer (either the Version Importer or the Baseline Importer), you are using RTC for versioning as well, and only using ClearCase for occasional access to archived versioned information that was not imported into RTC.
Comments
Robert Gormally
commented Jun 04 '14, 8:25 a.m.
Thanks Geoffrey!
There is no technical limitation that makes any RTC features unavailable while you use ClearCase Bridge, as far as I know. You can use Jazz Team Build while you continue to use ClearCase UCM. This video may help you:
Robert Gormally
commented Jun 04 '14, 11:58 a.m.
Thanks Masabumi!
Oh, if you compare ClearCase and RTC SCM, you'd find many differences. You may find a summary of the change in one slide of the enablement session recording:
Robert Gormally
commented Jun 05 '14, 4:35 a.m.
Ah yes, I see on slide 4 that Process Integration is specific to RTC SCM.
1
There's no simple answer for you about large deployments because it really depends on your CC or RTC deployments ( machines, network topology, database, etc.). I'd say CC and RTC has different approach to scale to large deployment, and CC has longer history of supporting large deployments successfully.
showing 5 of 6
show 1 more comments
|
Hi Robert,
configuring the bridge is easily done (I would say an hour the first time, every additional project/component will take minutes), while doing a migration from one SCM system to an other can take weeks, based on the repository size, team size, complexity of development environment and so on. So what is the goal? If it is the integration (UCM) ChangeSet - RTC task, the bridge would be the solution. If you have problems with CC UCM, which can be solved with RTC SCM (I remember some refactoring issues in CC), a migration can make sense. Regarding size of a project in UCM: In UCM you can use rootless components containing rooted components, and also rootless components, based on rootless components. I know projects having: rootless "system" component containing rootless "sub-system" component containing rootless "component" component containing rooted "module" component Such combinations are not possible in RTC afaik. greetings georg. |
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.