Committing to a company-wide software change is no small feat, but if you’re already sweating at the mere thought of checking code in and out, it’s time to plan your escape route.
So, break free and join Tom Tyler, Senior Consultant at Perforce and in-house ClearCase specialist to map out:
- Baseline-and-branch vs. detail history import strategies
- Porting
- Integrations for defect trackers, training, and tooling
- Cutover strategies
Full Text: Tom started his career at the NASA Kennedy Space Center and has consulted as a software developer and development environment architect in many software development organizations. Clients and colleagues knew Tom as “The ClearCase Guy” before discovering Perforce in 1999. Since then he has trained, mentored, and consulted with many Perforce customers large and small on topics such as branching strategies, application life cycle management, high availability and disaster recovery, configuration management, systems integrations, build automation, and more. He is a regular speaker at Perforce user conferences, has authored many white papers and blogs, and is a contributor to the National Consensus Standard for Configuration Management. He hails from Nashua, NH, where he lives with his wife and two sons.
Travel with a Guide!
Don’t be a pioneer!
Record Merges: “Just Enough” Branching History
Renaming: Tooling Exists, but Not Proven
Let’s talk about what history do and don’t get in that last diagram …
You lose content of files at each checkin, author of each chunk of text changed, timestamp of each change.
Record Merges: “Just Enough” Branching History
Renaming: Tooling Exists, but Not Proven
Simplified View: Time to distill and clean”uninteresting history”, such as changes to branching strategy over the years.
Sparse Import: Think of what you would see in a VOB without the benefit of a view -- sparsely populated structure.
Sparse Import: Think of what you would see in a VOB without the benefit of a view -- sparsely populated structure.
Missing Users: ClearCase relied on the OS for mapping userids to user names, where Perforce stores user information. The problem we see is that users who have left and had their accounts remove show up as something like “592” instead of something like “jsmith.”
UCM Quirks: Overzealous labeling, Activities can reference more than one version of the same file. These don’t map to Perforce.
Verify like you’re depending on the dry-run imports to do your real job. Because soon you will be.