0
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 19...
You’re Here Because ...
A Bit About You?
•  The topic sounded interesting and I'm just
curious. There’s no immediate busin...
Agenda
• 

Critical Milestones

• 

Migration Approaches
–  Tips
–  Baseline & Branch Import (“BBI”)
–  Detailed History I...
Critical Milestones
• 

Executive Decision:
We’re Going to Perforce!

• 

Transition Team Ready
—  Team Selected
—  Team T...
Critical Milestones
• 

Dry Runs Completed
—  Full Dry Runs (Stress & Load)
—  Data & process snags addressed
—  Pilot / P...
Branching Strategy
Mapping the Flow of Change
REL1.1

REL1
REL2

MAIN (fka “trunk”)

Team B
Team A

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 “int...
Tips – Latest Files, No History

10
Tips – Latest Files, No History

11
Tips – Latest Files, No History

All files have only 1 rev.

12
Tips – Latest Files, No History

All files have only 1 rev.
One Changelist

13
Baseline & Branch Import (BBI)

14
Baseline & Branch Import (BBI)

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

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

1...
Baseline & Branch Import (BBI)

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

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

1...
Baseline & Branch Import (BBI)

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

//fgs/Jam/MAIN/src/README
//fgs/Jam/dev/Port_OSX/src/README
On...
Baseline & Branch Import (BBI)

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

//fgs/Jam/MAIN/src/README
//fgs/Jam/dev/Port_OSX/src/README
Ap...
Detailed History Import
Read-Only Import Area to “Life In Perforce” Structure

//fgs/main/…

//i_svn/fgs/trunk/…

20
DHI - File History

21
DHI - File History

22
DHI – Folder History

23
DHI – Folder History

24
DHI – Folder History

25
DHI – Folder History

26
Transition and Cutover
•  Grand Opening
–  Friday Subversion, Monday Perforce!

•  Phased by Team
–  Beware software depen...
Subversion Migration Tech Tips
•  Case Issues: Convert on same platform as server
•  Provision Adequate Hardware Resources...
Subversion Migration Tech Tips
•  Handling SVN Properties
–  Use Perforce Attributes

•  Handling SVN Externals
–  Use fle...
Why Migrate? Top 6
Drivers

Benefits

•  Vastly more powerful
branching & merging

•  A whole ‘nother level of
capability
...
Customer Experience

“

I want to take this opportunity to
acknowledge an outstanding job done
by you supporting us throug...
Customer Experience

“

I also had boasted the lofty goal before
we executed the migration that I was
aiming for zero loss...
Customer Experience

“

I have had several people comment
to me that they are impressed at
how smooth the whole migration
...
Thank You!
Please Send us Your Questions!

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

Migration Planning
Migration Approaches
Technical Snags
Transition and ...
Resources
•  Website: www.perforce.com
•  Visit the Multimedia Library
•  Demo: eval-demo@perforce.com
•  Support: support...
Upcoming SlideShare
Loading in...5
×

Subversion to Perforce in 30 minutes

482

Published on

Contemplating a move from Subversion? Learn what you need to start planning your migration.

Tom Tyler, Senior Consultant at Perforce Software, shares practical tips to plan your migration, allay your concerns and prevent a wasteful, misdirected effort.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
482
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Subversion to Perforce in 30 minutes"

  1. 1. Subversion to Perforce in 30 minutes Tom Tyler, Perforce Software Consulting Services
  2. 2. 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
  3. 3. You’re Here Because ... A Bit About You? •  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. 3
  4. 4. Agenda •  Critical Milestones •  Migration Approaches –  Tips –  Baseline & Branch Import (“BBI”) –  Detailed History Import (“DHI”) •  Transition and Cutover •  Technical Tips •  Customer Experience 4
  5. 5. 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
  6. 6. 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
  7. 7. Branching Strategy Mapping the Flow of Change REL1.1 REL1 REL2 MAIN (fka “trunk”) Team B Team A 7
  8. 8. Perforce Directory Standard (PDS) perforce.com/blog http://info.perforce.com/PDS.html 8
  9. 9. 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
  10. 10. Tips – Latest Files, No History 10
  11. 11. Tips – Latest Files, No History 11
  12. 12. Tips – Latest Files, No History All files have only 1 rev. 12
  13. 13. Tips – Latest Files, No History All files have only 1 rev. One Changelist 13
  14. 14. Baseline & Branch Import (BBI) 14
  15. 15. Baseline & Branch Import (BBI) //fgs/Jam/3.0-r/src/README //fgs/Jam/MAIN/src/README //fgs/Jam/dev/Port_OSX/src/README 15
  16. 16. Baseline & Branch Import (BBI) //fgs/Jam/3.0-r/src/README //fgs/Jam/MAIN/src/README //fgs/Jam/dev/Port_OSX/src/README 16
  17. 17. Baseline & Branch Import (BBI) //fgs/Jam/3.0-r/src/README //fgs/Jam/MAIN/src/README //fgs/Jam/dev/Port_OSX/src/README One Changelist and description per Baseline. 17
  18. 18. Baseline & Branch Import (BBI) //fgs/Jam/3.0-r/src/README //fgs/Jam/MAIN/src/README //fgs/Jam/dev/Port_OSX/src/README Approximately same “time of import” timestamp for all Changelists/Baselines. 18
  19. 19. Detailed History Import Read-Only Import Area to “Life In Perforce” Structure //fgs/main/… //i_svn/fgs/trunk/… 20
  20. 20. DHI - File History 21
  21. 21. DHI - File History 22
  22. 22. DHI – Folder History 23
  23. 23. DHI – Folder History 24
  24. 24. DHI – Folder History 25
  25. 25. DHI – Folder History 26
  26. 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
  27. 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
  28. 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
  29. 29. Why Migrate? Top 6 Drivers Benefits •  Vastly more powerful branching & merging •  A whole ‘nother level of capability •  Scalability •  A whole ‘nother level of scalability •  Better Visualizations (GUI) •  Preference for Best of Breed •  Faster •  Standardization and Consolidation •  Faster/better merges and detection of need to merge •  Put Developers at the top of their craft •  Faster •  Better ROI on Backup, HA/DR Solutions, Infrastructure 30
  30. 30. 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
  31. 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
  32. 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
  33. 33. Thank You! Please Send us Your Questions! 34
  34. 34. You’d like to know more about .... •  •  •  •  •  Migration Planning Migration Approaches Technical Snags Transition and Cutover Details of DHI Tools Polling Question 35
  35. 35. Resources •  Website: www.perforce.com •  Visit the Multimedia Library •  Demo: eval-demo@perforce.com •  Support: support@perforce.com •  Consulting: consulting@perforce.com •  Phone: 510-864-7400 36
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×