Save story from Clearcase to Git?

In my company, we are moving (completely) from ClearCase UCM to Git. We will not use Clearcase after a while using Git.

Are there any good tools in the transition that somehow bring the story from ClearCase to Git?

Also, I read a lot that one component = one repo. However, we want to reorganize and break the current component into smaller parts. (The person who created ClearCase didn't really plan ahead.) Is there a way to do this?

Any comments would be appreciated - including answers and other things that you should pay attention to during the transition.

+8
git clearcase clearcase-ucm
source share
3 answers

At least with ClearCase UCM you have complete baselines for working, that is, tags that are installed in all files of this component.

From experience, you never import the entire history from ClearCase into a revision control tool based on a link (see the difference between ClearCase and Git : ClearCase has a history file by file, not a โ€œrevision by revisionโ€)

What I usually do, as I mention in my answer, " Sync GIT and ClearCase ":

  • one GIT repo per UCM component
  • import only the last 3 or 4 baselines for the integration stream
  • import several baselines from substreams only if it is really necessary
  • Lock UCM vob and keep ClearCase read-only for archive
+6
source share

Try this tool to import history from ClearCase to git: https://github.com/charleso/git-cc

Regarding the repository reorganization when switching from ClearCase to git, there were few discussions on SO, for example: Synchronize GIT and ClearCase

+3
source share

I would not immediately delete a clear case. What you want to do is capture the prompts of any branches in the clear case and any tags. This should be done in such a way as to reflect what happened in the clear case (to preserve the points of the logical branch, etc.). Use git from now on. If you need to delve into history, go to business. In the end, archive the clear case and only restore it if you are in a binding to see some old commits. Importing an old story is not worth the trouble in my experience. This is often time consuming and error prone.

+3
source share

All Articles