Subversion to Perforce in 30 minutes

Subversion to Perforce in 30 minutes

Tom Tyler, Perforce Software Consulting Services

Speaker: Tom Tyler

Tom Tyler is a Senior Consultant at Perforce. He started his career at NASA Kennedy Space Center in 1990, and has worked as a developer and consultant in various software development organizations. Colleagues knew Tom as “The ClearCase Guy” before he discovered Perforce in 1999. He has since been consulting with Perforce customers large and small.

2

You’re Here Because ...

•  The topic sounded interesting and I'm just curious. There’s no immediate business need.

•  We're contemplating a migration to Perforce.

•  We're committed to migrate to Perforce, and hoping this helps informs our planning

•  We migrated already, and want to see if we missed anything.

A Bit About You?

3

Agenda

•  Critical Milestones •  Migration Approaches

–  Tips

–  Baseline & Branch Import (“BBI”)

–  Detailed History Import (“DHI”)

•  Transition and Cutover

•  Technical Tips

•  Customer Experience

4

Critical Milestones

•  Executive Decision: We’re Going to Perforce!

•  Transition Team Ready —  Team Selected

—  Team Trained

•  Migration Plan Ready — Migration Approaches Selected

— Cutover Strategy Defined

—  Transition Strategy Identified

—  Transition Schedule Identified

—  Branching Strategy Planned

5

Critical Milestones

•  Dry Runs Completed —  Full Dry Runs (Stress & Load)

— Data & process snags addressed

—  Pilot / POC

•  Perforce Environment Ready — Migrated Source Code Verified

—  Build Systems Retooled

—  Build Results Verified

•  Users Trained •  Live on Perforce!

6

Branching Strategy Mapping the Flow of Change

REL2

MAIN (fka “trunk”)

REL1

REL1.1

Team A

Team B

7

Perforce Directory Standard (PDS)

perforce.com/blog http://info.perforce.com/PDS.html

8

Migration Approaches

•  Tips Only

–  Copy tips into new system.

•  Baseline & Branch Import (BBI) -  Bring along only “interesting” history – key

baselines and high-level branch operations.

•  Detailed History Import (DHI) –  Bring historical details into Perforce.

9

Tips – Latest Files, No History

10


11


12

All files have only 1 rev.


13

One Changelist

All files have only 1 rev.

Baseline & Branch Import (BBI)

14


//fgs/Jam/dev/Port_OSX/src/README

//fgs/Jam/MAIN/src/README

//fgs/Jam/3.0-r/src/README

15





16





17

One Changelist and description per Baseline.





18

Approximately same “time of import” timestamp for all Changelists/Baselines.

Detailed History Import Read-Only Import Area to “Life In Perforce” Structure

//i_svn/fgs/trunk/…

//fgs/main/…

20

DHI - File History

21

DHI - File History

22

DHI – Folder History

23


24


25


26

Transition and Cutover

•  Grand Opening –  Friday Subversion, Monday Perforce!

•  Phased by Team

–  Beware software dependencies. –  Beware dependencies of collaborating teams. –  Limitations of migration utilities can limit cutover options.

27

Subversion Migration Tech Tips

•  Case Issues: Convert on same platform as server •  Provision Adequate Hardware Resources! •  Typemap, file types, and Unicode •  SVN Empty directories

–  Use ‘.d’ or README files

–  Make dirs in build/deploy files, Makefiles, etc.

28

Subversion Migration Tech Tips

•  Handling SVN Properties –  Use Perforce Attributes

•  Handling SVN Externals –  Use flexibility of Workspace Mapping

–  Add Version Specifier files

•  Keep SVN around for a while

29

Why Migrate? Top 6

30

Drivers Benefits •  Vastly more powerful

branching & merging •  A whole ‘nother level of

capability

•  Scalability •  A whole ‘nother level of scalability

•  Better Visualizations (GUI) •  Faster/better merges and detection of need to merge

•  Preference for Best of Breed •  Put Developers at the top of their craft

•  Faster •  Faster

•  Standardization and Consolidation

•  Better ROI on Backup, HA/DR Solutions, Infrastructure

Customer Experience

I want to take this opportunity to acknowledge an outstanding job done by you supporting us through our Perforce migration.

- Perforce Customer

31

“ ”

Customer Experience

I also had boasted the lofty goal before we executed the migration that I was aiming for zero loss of productivity to our <snip> project as the result of this migration. I think I can make a case that this came true, also. - Perforce Customer

32

“

”

Customer Experience

I have had several people comment to me that they are impressed at how smooth the whole migration process has been. - Perforce Customer

33

“ ”

Thank You!

Please Send us Your Questions!

34

You’d like to know more about ....

•  Migration Planning •  Migration Approaches •  Technical Snags •  Transition and Cutover •  Details of DHI Tools

Polling Question

35

Resources

•  Website: www.perforce.com •  Visit the Multimedia Library •  Demo: [email protected] •  Support: [email protected] •  Consulting: [email protected] •  Phone: 510-864-7400

36

Subversion to Perforce in 30 minutes

Technology

Transcript of Subversion to Perforce in 30 minutes