Home/ Questions/Q 8545297
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T12:45:38+00:00

At my company, we are transitioning (fully) from ClearCase UCM to Git. We will

  • 0

At my company, we are transitioning (fully) from ClearCase UCM to Git. We will not be using Clearcase after some time using Git.

In the transition, are there any good tools that will bring the history from ClearCase into Git somehow?

Also, I have read a lot that one component = one repo. However, we want to reorganize and split the current component into smaller parts. (The person that set up ClearCase didn’t really plan ahead.) Is there also a way to do this?

Any comments would be appreciated – including answers and other things to watch out for during the transition.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    At least, with ClearCase UCM, you have full baselines to work with, that is labels which are set on all the files of a given component.

    By experience, you never import the full history from ClearCase to a Version Control Tool which is based on revision across the the referential (see the difference between ClearCase and Git: ClearCase has an history set file by file, not “revision by revision”)

    What I usually do, as I mention in my answer “Sync GIT and ClearCase” is:

    • one Git repo per UCM component
    • import only the last 3 or 4 baselines for the Integration Stream
    • import a few baselines from sub-Streams only if it is really needed
    • Lock the UCM vob and keep ClearCase in read-only mode for archive
    • 0