They didn’t think migrating off their legacy version control system would be difficult. They thought it would be impossible.
For Cadence Design Systems, the multinational electronic design automation (EDA) software and engineering services company, moving off ClearCase was an important but daunting goal.
They knew a modern, flexible system would foster innovation and help them keep up with rapidly evolving customer demands. But, they had a highly customized environment and wanted to preserve the data they’d accumulated over the years.
It wasn’t easy. But, with Perforce, it was possible.
How? Find out.
Cindi Hunter, Director of Configuration Management and Tom Tyler, Senior Consultant at Perforce Software, share their highly successful migration process, which includes:
• Defining the scope of your migration given your unique environment.
• Determining a migration strategy to preserve sophisticated branching strategies, custom tools, and important data.
• Ensuring you get the migration support you need from your new vendor.
23. Follow us for news and insights!
Visit www.perforce.com
Notas do Editor
Cindi Hunter, Director SPB Configuration Management
Cindi joined Cadence in 1995 as the first CM build engineer for Cadence’s first Window’s based product Allegro Designer. Since then Cindi has supported the SPB engineering groups for over 21 years. This included several source control migrations from RCS, to ClearCase, and eventually Perforce. Cindi and her team support over 150 engineers spanning 6 different countries.
Tom Tyler, Senior Consultant at Perforce Software
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. Tom trains, mentors, and consults with 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.