Cvs To Clear Case

IBM Global Business Services

04/10/23 © 2007 IBM Corporation

Migration from CVS to ClearCase

By Roberto De Palma


© 2007 IBM Corporation2

Objective of the presentation

Current problem with our Change Management Process

Difference between CVS and ClearCase

Risk and Impact for migrating to ClearCase

Cost and benefits for migrating to ClearCase



Agenda

What are our current issues with our Change Management

What is Change Management

CVS: What it is and what it’s not

ClearCase vs CVS

ClearCase Overview

ClearCase Benefit

Solution With ClearCasePlan of migration

Risk of the migration

Conclusion

Period of questions and comments




Don’t know witch files is in witch release

Developers don’t have there own environment

Managing the ticket

– Developers spends a average 2hr before starting working

– Witch fix are in witch release?

• Impact witch module, class

Process issues




CVS Administration

– No Report, need to use another tool

– Lack of security

• Anybody can do anything– Create/Delete Branch, Tag or File

– Management is not simple

CVS Developer User

– Weak merging process

– Need to commit each file separately for saying witch RT

CVS Tool issues




When people talk about CM, they are usually referring to the tools that manage source code. However, this is just one aspect of the solution. If you step back and look at all of the components, CM consists of many different pieces, including: :

1. Identification: identifying components, structure

2. Control: controlling releases, visibility and changes (i.e. via branches)

3. Status: ability to report status, changes, and their impacts

4. Audit: ability to validate completeness and track changes (i.e. history that is kept even after name changes)

5. Manufacture: ability to trace the process from the individual developer who makes a change through to the release of the software

6. Process: ensuring that changes go through a particular lifecycle

7. Teamwork: ability to control team interactions at multiple levels




ClearCase is a tool that supports all of these components

Change management is all about managing the increasing complexity of a project, plain and simple.



CVS: What it is

CVS is a basic version control system

It provides project-oriented version control for files only, storing changes to files as deltas

With CVS, users can:

– track a file’s change history from creation to most recent version

– share files between projects

– merge changes from two different file versions into one file



CVS: What it’s not CVS is not a substitute for management.

– Your managers and project leaders are expected to talk to you frequently enough to make certain you are aware of schedules, merge points, branch names and release dates. If they don't, CVS can't help.

CVS is not a substitute for developer communication.

– CVS cannot determine when simultaneous changes within a single file, or across a whole collection of files, will logically conflict with one another.

CVS does not have change control

– No change set or bug tracking

CVS does not have a built-in process model



ClearCase vs CVS

Features CVS ClearCase

Client Server Access Meth. YES YES

Client Tools on Most Platform YES YES

Open Source YES No

Build-in Process (UCM) No YES

Build Management No YES

Change Cont. (change set) No YES

Multisite No YES



ClearCase vs CVS


Parallel Development Limit. YES

Merging 2 contributes & Text only

YES

Branching Not Robust YES

Files Control YES YES

Directories Control No YES

Native GUI No YES

Reporting No YES



ClearCase vs CVS


Snapshot Views YES YES

Dynamic Views (MVFS) No YES

Triggers Lim. YES

Integrations Lim. YES

History YES YES



ClearCase Overview

Integrates with IBM Rational ClearQuest to provide software configuration management support.

ClearCase and ClearQuest support an out of the box process – Unified Change Management (UCM).

Out of the box integrations with a number of industry-leading IDEs

– WebLogic Workshop

– IBM Rational suite

– And more

Has a number of intuitive, easy to use interfaces.

Supports a wide range of operating systems:

– ClearCase supports many versions of Windows, UNIX and Linux operating systems

ClearCase provides reporting tools out of the box.



ClearCase Benefit

The benefit of ClearCase

– Free up your team from the time-consuming and repetitive tasks

Branching and Merging.

– ClearCase makes available several tool integrations to help merge Microsoft Word® and HTML documents, providing a standard that is not offered by normal ASCII text merging tools.



ClearCase Benefit

ROI

– ClearCase will help you improve the accuracy of your project releases, automate those competitive tasks, and manage your team across multiple workspaces.

– But CVS it’s free, is it?• Freeware such as CVS has a low price but as high a cost as

any other SCM tool, possibly higher.• It’s take for the xDist Dev 3-4 hour for merging• Now we have 13 branch in CVS, how much branch will

there be in 6 month, 1 years, 5 years. How do we manage all this?

• It’s take for the xDist Dev 2 hour for analyzing a ticket before starting coding



Recap – Problem with our CM

Don’t know witch files is in witch release

Developers don’t have there own environment

Managing the ticket

– Developers spends a average 2hr before starting working

– Witch fix are in witch release?

• Impact witch module, class

Process issues



Recap – Problem with our CM

CVS Administration

– No Report, need to use another tool

– Lack of security

• Anybody can do anything– Create/Delete Branch, Tag or File

– Management is not simple

CVS Developer User

– Weak merging process

– Need to commit each file separately for saying witch RT

CVS Tool issues



Solution With ClearCase

ClearCase enable you to know with version of a file is in with release

ClearCase enable developers to have their own set of environment

ClearCase is more easy to manage

– Set security permission for user

– Generate report

ClearCase as a Stronger Branching and Merging Process

– Need to have to proper rights for creating or deleting branch

– Can merge Microsoft Word® ,HTML or XML documents, a standard that is not offered by normal ASCII text merging tools



Plan of migration

We could install ClearCase in our own infrastructure (eliminated)

– More Risk then WW Infrastructure

WW Infrastructure DST + service:

– $40-50 per project / per VOB (2 GB) / per month

– Establish servers and tools

– Setup Admin (user ids, access level)

– Look at licensing details

– Provide 24X5 support

– Weekend Page Support is available (and if required and provided with advance notice, will have resources available)

– Web interface that will allow Client access to these tools and infrastructure (June 2007) (cost is to be confirm)



Plan of migration

2-3 month of planning

CM Workshop (1 day)– ClearCase Administrator, Project Lead, Architect, CoC Specialist

Analyzing and conception of the structure of the vobs (1 day)– 1 Architect, 1 Developer, ClearCase Admin

Setup– Preparing Readiness Plan (2 days)

• CoC Specialist– Installation and Configuration

• CoC Specialist (5 days), ClearCase Administrator (2 days)• Configuration of the VOBs• Security

– Role and Responsibility– Installing the client tool on each user (1 day)

• ClearCase Administrator



Plan of migration

Training (Self + w/CoC Member)– ClearCase Administrator (4 days)– Team Lead (2 days)– Developer (1 day)

Documentation (10 days)– ClearCase Administrator, Developer

Testing (4-5 day)– 1 Developer and ClearCase Admin



Plan of migration

Some question that we need to answer during the workshop

– How big do you think the project will be?

– How many people will be involved in the product development?

– At how many locations will the product be developed, tested, and deployed?

– Is the product internal or external?

– What are the third party tools that you will be using?

– What is the development cycle of the product?

– How do your current development methodologies fit into your tool plans?

– Are any key roles missing from your team?

– Do you have the hardware you need?

– Do you have the infrastructure ready to support your plans?



Risk of migration

Period of transition for the people

Down time

Duplication of effort

Decreased productivity

It's not easy to change the VOB structure after establishing a structure and locating source code into the VOBs.

Assigning Role/Responsibility to people

– ClearCase Administrator

– Integrator

– Etc.



Conclusion

The migration should be plan and drive as a project

– Take more time at the beginning but it reduce the risk of failure or the rejection of change

– At least one person on each role should participate in the testing

– Plan a head and be prepare to perform the migration during the week-end

ClearCase can not solve all our problem of CM

– Should look at ClearQuest for managing tickets

– BuildForge may help us for the building process



Questions and comments



Annex ClearCase Overview

Very fast workspace, view, and creation. Most other tools require a complete "checkout" in order to see files in your project. With ClearCase, you can start working with views right away. This decreases the time engineers need to wait to start working.

Build avoidance and derived object sharing. If you have a large project that takes time to build, you can take advantage of ClearCase's derived object mechanism for "making" the product. This prevents files from being compiled or linked again before your engineers use them. This further decreases the amount of time it takes to get an engineer working on a problem.

Connecting additional data to elements. There always seems to be additional information that we need to store about the project, file, or directory. ClearCase has a simple interface for adding additional information to a ClearCase element or version. This data can be queried, modified, and removed. This prevents the scattering of information about the project, which typically happens over time.



AnnexClearCase Overview

Directory versioning. Several CM tools do not have directory versioning; they only version files. This is advantageous in situations where users need to roll back to view previously created sets of artifacts.

Multi-site development. ClearCase has a good multi-site development tool that allows multiple locations to work on the same code at the same time. It has the benefit over most other tools because it only moves changes across the net. It is highly customizable, and by far the best solution for multi-site development out there.

Branching and Merging. Although other CM systems have branching and some merging tools, ClearCase by far has the best tools and algorithms for handling complex merging problems. In addition to traditional text merging, ClearCase makes available several tool integrations to help merge Microsoft Word® and HTML documents, providing a standard that is not offered by normal ASCII text merging tools.

Cvs To Clear Case

Documents

Transcript of Cvs To Clear Case