Loading...

jobs/job000236

job000236

tardis (tardis)
tardis created this job 10 years ago, modified by Perforce maintenance 6 years ago
Open
Add support for migration into stream depot.
It would be helpful to be able to migrate the history directly into a stream depot rather than a normal depot and then restructuring afterward. This is especially true if all you have is a trunk and no branches or tags.
Status
Open
Project
perforce-software-p4convert
Severity
B
Reported By
tardis
Reported Date
10 years ago
Modified By
Perforce maintenance
Modified Date
6 years ago
Owned By
tardis
Type
Feature
paul_allen (Paul Allen)
Paul Allen commented 10 years ago

This is non trivial...

No one has written a Perforce classic to Streams converter; that is hard enough, but CVS/SVN to Streams would be even more of a challenge.

  1. All the paths in Subversion would need to be remapped as streams has a rigid branch structure.
  2. Hierarchy would need to be calculated from Subversion to determine stream type.
  3. A stream to stream map would need to be built based on the Subversion history.
  4. Integration records would need to be trimmed or mapped to the stream to stream mappings.

Rumor is that 15.2 or later Streams might relax the rigid branch structure, but until then I would suggest using Populate to seed new streams and Import mappings to bring in other content.
Reply