We have to migrate from base clearcase to UCM.
We have to move our Vobs from Base clearcase to Clearcase UCM.
Few of the steps were suggested by other teams.
It is quite easy (for the ClearCase setup. I won't address the UCM training part, which is not relevant to your question).
You don't have to move the vobs.
There is no such thing as "mount base clearcase vobs to UCM" or "UCM Vob".
A Vob can contains elements managed by base ClearCase, and UCM component at the same time.
The only constraint you need to be aware is that an UCM component has its root directly one level below the vob:
aVob\aCmp1
aVob\aCmp2
...
So, as long as all your future UCM components have their elements already (in your current base ClearCase config) in the first directory of a Vob, you can:
Cmp1
at any time, with its root directory at \aVob\aCmp1
The PVob will be there to record your projects, Streams, and component definitions.
The OP Samselvaprabu adds in the comments:
How to move all the files and directories from base to UCM. Should we copy, paste from Base to UCM and check-in all(using clearfsimport) or Clearcase itself has some nice ways to move the contents from base to UCM?
Short answer? You do not "move to UCM":
(longer answer)
The only "move" you make is to make sure your data are organize under the first level of a Vob.
That means simple "cleartool move
" of your data within a Vob.
No clearfsimport
or any UCM commands required.
If you had some set of files you wish to declare as a component, and were stored in \myVob\my_projects\p1
, just move p1
(which will keep all its history) under \myVob
: \myVob\p1
.
That's it.
Nothing more to do.
Then, once your data are correctly organized, you just:
\myVob\p1
.When a component is declared, the only limitation is that you won't be able to move elements within p1
outside of \myVob\p1
.
But you can still move them, checkout and checkin them freely within \myVob\p1
.
From base ClearCase views, or from UCM views.
Having a component declared at \myVob\p1
doesn't include any other special limitations on the elements within that root directory. They aren't "transformed", keep their history, and can be used in base or in UCM at will.