Transfer bandwidth

Question

I have a large amount of clear data that needs to be transferred to perforce. The changes span most of the decade, and I need to keep as much information as possible about the branch and tags. In addition, we make extensive use of symbolic links, which are maintained in clarity, but not in force. What tips or tools can you offer that can make this easier?

Answer 1

The first step is to decide whether to migrate all or only certain key versions. If you transfer only important versions (releases and milestones), you will get a much simpler story in Perforce, without losing anything important. Then ClearCase can be stored as a historical archive, if ever needed. (If IBM hasn’t made a difference, ClearCase licenses do not expire when maintenance ends, you simply lose the right to new updates and patches and gain access to support)

, Perforce - , 1:1 . - ; , Perforce ClearCase.

, Perforce , http://perforce.com/perforce/ccaseconv.html , .

Answer 2

Google "clearcase to perforce conversion" . ClearCase Perforce Conversion Guide. , (1), , (2) , , . , .

- , Perforce, ClearCase, , - , , -Perforce ...

Answer 3

. CC- > Perforce , . http://www.perforce.com/sites/default/files/pdf/migration-planning-guide-clearcase-to-perforce.pdf

Answer 4

, , - , , (, , ..)

, () , , ( ). () , perforce, : .

, , . / - , . ( perforce dir-vers.), clearcase ( !).

, : : VOB (, 10 , 50 ), , . devteam .

Answer 5

, ClearCase Perforce.
ClearCase Perforce Conversion Guide:

Perforce ; ClearCase .

, ; Perforce , - Perforce .
, //depot/projecta 42

p4 sync //depot/projecta/...@42

This means that the ClearCase project that was imported was UCM one , since the baseline concept follows one of the global changes. Only files with a baseline were imported, other versions were discarded.