Your SlideShare is downloading. ×
0
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Cvs To Clear Case
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Cvs To Clear Case

3,774

Published on

Migration from CVS to ClearCase

Migration from CVS to ClearCase

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
3,774
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. Migration from CVS to ClearCase By Roberto De Palma
    • 2. Objective of the presentation <ul><li>Current problem with our Change Management Process </li></ul><ul><li>Difference between CVS and ClearCase </li></ul><ul><li>Risk and Impact for migrating to ClearCase </li></ul><ul><li>Cost and benefits for migrating to ClearCase </li></ul>
    • 3. Agenda <ul><li>What are our current issues with our Change Management </li></ul><ul><li>What is Change Management </li></ul><ul><li>CVS: What it is and what it’s not </li></ul><ul><li>ClearCase vs CVS </li></ul><ul><li>ClearCase Overview </li></ul><ul><li>ClearCase Benefit </li></ul><ul><li>Solution With ClearCase Plan of migration </li></ul><ul><li>Risk of the migration </li></ul><ul><li>Conclusion </li></ul><ul><li>Period of questions and comments </li></ul>
    • 4. What are our current issues with our Change Management <ul><li>Don’t know witch files is in witch release </li></ul><ul><li>Developers don’t have there own environment </li></ul><ul><li>Managing the ticket </li></ul><ul><ul><li>Developers spends a average 2hr before starting working </li></ul></ul><ul><ul><li>Witch fix are in witch release? </li></ul></ul><ul><ul><ul><li>Impact witch module, class </li></ul></ul></ul>Process issues
    • 5. What are our current issues with our Change Management <ul><li>CVS Administration </li></ul><ul><ul><li>No Report, need to use another tool </li></ul></ul><ul><ul><li>Lack of security </li></ul></ul><ul><ul><ul><li>Anybody can do anything </li></ul></ul></ul><ul><ul><ul><ul><li>Create/Delete Branch, Tag or File </li></ul></ul></ul></ul><ul><ul><li>Management is not simple </li></ul></ul><ul><li>CVS Developer User </li></ul><ul><ul><li>Weak merging process </li></ul></ul><ul><ul><li>Need to commit each file separately for saying witch RT </li></ul></ul>CVS Tool issues
    • 6. What is Change Management <ul><li>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: : </li></ul><ul><ul><li>Identification : identifying components, structure </li></ul></ul><ul><ul><li>Control : controlling releases, visibility and changes (i.e. via branches) </li></ul></ul><ul><ul><li>Status : ability to report status, changes, and their impacts </li></ul></ul><ul><ul><li>Audit : ability to validate completeness and track changes (i.e. history that is kept even after name changes) </li></ul></ul><ul><ul><li>Manufacture : ability to trace the process from the individual developer who makes a change through to the release of the software </li></ul></ul><ul><ul><li>Process : ensuring that changes go through a particular lifecycle </li></ul></ul><ul><ul><li>Teamwork : ability to control team interactions at multiple levels </li></ul></ul>
    • 7. What is Change Management <ul><li>ClearCase is a tool that supports all of these components </li></ul><ul><li>Change management is all about managing the increasing complexity of a project, plain and simple. </li></ul>
    • 8. CVS: What it is <ul><li>CVS is a basic version control system </li></ul><ul><li>It provides project-oriented version control for files only, storing changes to files as deltas </li></ul><ul><li>With CVS, users can: </li></ul><ul><ul><li>track a file’s change history from creation to most recent version </li></ul></ul><ul><ul><li>share files between projects </li></ul></ul><ul><ul><li>merge changes from two different file versions into one file </li></ul></ul>
    • 9. CVS: What it’s not <ul><li>CVS is not a substitute for management. </li></ul><ul><ul><li>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. </li></ul></ul><ul><li>CVS is not a substitute for developer communication. </li></ul><ul><ul><li>CVS cannot determine when simultaneous changes within a single file, or across a whole collection of files, will logically conflict with one another. </li></ul></ul><ul><li>CVS does not have change control </li></ul><ul><ul><li>No change set or bug tracking </li></ul></ul><ul><li>CVS does not have a built-in process model </li></ul>
    • 10. ClearCase vs CVS YES No Multisite YES No Change Cont. (change set) YES No Build Management YES No Build-in Process (UCM) No YES Open Source YES YES Client Tools on Most Platform YES YES Client Server Access Meth. ClearCase CVS Features
    • 11. ClearCase vs CVS YES No Reporting YES No Native GUI YES No Directories Control YES YES Files Control YES Not Robust Branching YES 2 contributes & Text only Merging YES Limit. Parallel Development ClearCase CVS Features
    • 12. ClearCase vs CVS YES YES History YES Lim. Integrations YES Lim. Triggers YES No Dynamic Views (MVFS) YES YES Snapshot Views ClearCase CVS Features
    • 13. ClearCase Overview <ul><li>Integrates with IBM Rational ClearQuest to provide software configuration management support. </li></ul><ul><li>ClearCase and ClearQuest support an out of the box process – Unified Change Management (UCM). </li></ul><ul><li>Out of the box integrations with a number of industry-leading IDEs </li></ul><ul><ul><li>WebLogic Workshop </li></ul></ul><ul><ul><li>IBM Rational suite </li></ul></ul><ul><ul><li>And more </li></ul></ul><ul><li>Has a number of intuitive, easy to use interfaces. </li></ul><ul><li>Supports a wide range of operating systems: </li></ul><ul><ul><li>ClearCase supports many versions of Windows, UNIX and Linux operating systems </li></ul></ul><ul><li>ClearCase provides reporting tools out of the box. </li></ul>
    • 14. ClearCase Benefit <ul><li>The benefit of ClearCase </li></ul><ul><ul><li>Free up your team from the time-consuming and repetitive tasks </li></ul></ul><ul><li>Branching and Merging. </li></ul><ul><ul><li>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. </li></ul></ul>
    • 15. ClearCase Benefit <ul><li>ROI </li></ul><ul><ul><li>ClearCase will help you improve the accuracy of your project releases, automate those competitive tasks, and manage your team across multiple workspaces. </li></ul></ul><ul><ul><li>But CVS it’s free, is it? </li></ul></ul><ul><ul><ul><li>Freeware such as CVS has a low price but as high a cost as any other SCM tool, possibly higher. </li></ul></ul></ul><ul><ul><ul><li>It’s take for the xDist Dev 3-4 hour for merging </li></ul></ul></ul><ul><ul><ul><li>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? </li></ul></ul></ul><ul><ul><ul><li>It’s take for the xDist Dev 2 hour for analyzing a ticket before starting coding </li></ul></ul></ul>
    • 16. Recap – Problem with our CM <ul><li>Don’t know witch files is in witch release </li></ul><ul><li>Developers don’t have there own environment </li></ul><ul><li>Managing the ticket </li></ul><ul><ul><li>Developers spends a average 2hr before starting working </li></ul></ul><ul><ul><li>Witch fix are in witch release? </li></ul></ul><ul><ul><ul><li>Impact witch module, class </li></ul></ul></ul>Process issues
    • 17. Recap – Problem with our CM <ul><li>CVS Administration </li></ul><ul><ul><li>No Report, need to use another tool </li></ul></ul><ul><ul><li>Lack of security </li></ul></ul><ul><ul><ul><li>Anybody can do anything </li></ul></ul></ul><ul><ul><ul><ul><li>Create/Delete Branch, Tag or File </li></ul></ul></ul></ul><ul><ul><li>Management is not simple </li></ul></ul><ul><li>CVS Developer User </li></ul><ul><ul><li>Weak merging process </li></ul></ul><ul><ul><li>Need to commit each file separately for saying witch RT </li></ul></ul>CVS Tool issues
    • 18. Solution With ClearCase <ul><li>ClearCase enable you to know with version of a file is in with release </li></ul><ul><li>ClearCase enable developers to have their own set of environment </li></ul><ul><li>ClearCase is more easy to manage </li></ul><ul><ul><li>Set security permission for user </li></ul></ul><ul><ul><li>Generate report </li></ul></ul><ul><li>ClearCase as a Stronger Branching and Merging Process </li></ul><ul><ul><li>Need to have to proper rights for creating or deleting branch </li></ul></ul><ul><ul><li>Can merge Microsoft Word® ,HTML or XML documents, a standard that is not offered by normal ASCII text merging tools </li></ul></ul>
    • 19. Plan of migration <ul><li>We could install ClearCase in our own infrastructure (eliminated) </li></ul><ul><ul><li>More Risk then WW Infrastructure </li></ul></ul><ul><li>WW Infrastructure DST + service: </li></ul><ul><ul><li>$40-50 per project / per VOB (2 GB) / per month </li></ul></ul><ul><ul><li>Establish servers and tools </li></ul></ul><ul><ul><li>Setup Admin (user ids, access level) </li></ul></ul><ul><ul><li>Look at licensing details </li></ul></ul><ul><ul><li>Provide 24X5 support </li></ul></ul><ul><ul><li>Weekend Page Support is available (and if required and provided with advance notice, will have resources available) </li></ul></ul><ul><ul><li>Web interface that will allow Client access to these tools and infrastructure (June 2007) (cost is to be confirm) </li></ul></ul>
    • 20. Plan of migration <ul><li>2-3 month of planning </li></ul><ul><li>CM Workshop (1 day) </li></ul><ul><ul><li>ClearCase Administrator, Project Lead, Architect, CoC Specialist </li></ul></ul><ul><li>Analyzing and conception of the structure of the vobs (1 day) </li></ul><ul><ul><li>1 Architect, 1 Developer, ClearCase Admin </li></ul></ul><ul><li>Setup </li></ul><ul><ul><li>Preparing Readiness Plan (2 days) </li></ul></ul><ul><ul><ul><li>CoC Specialist </li></ul></ul></ul><ul><ul><li>Installation and Configuration </li></ul></ul><ul><ul><ul><li>CoC Specialist (5 days), ClearCase Administrator (2 days) </li></ul></ul></ul><ul><ul><ul><li>Configuration of the VOBs </li></ul></ul></ul><ul><ul><ul><li>Security </li></ul></ul></ul><ul><ul><ul><ul><li>Role and Responsibility </li></ul></ul></ul></ul><ul><ul><li>Installing the client tool on each user (1 day) </li></ul></ul><ul><ul><ul><li>ClearCase Administrator </li></ul></ul></ul>
    • 21. Plan of migration <ul><li>Training (Self + w/CoC Member) </li></ul><ul><ul><li>ClearCase Administrator (4 days) </li></ul></ul><ul><ul><li>Team Lead (2 days) </li></ul></ul><ul><ul><li>Developer (1 day) </li></ul></ul><ul><li>Documentation (10 days) </li></ul><ul><ul><li>ClearCase Administrator, Developer </li></ul></ul><ul><li>Testing (4-5 day) </li></ul><ul><ul><li>1 Developer and ClearCase Admin </li></ul></ul>
    • 22. Plan of migration <ul><li>Some question that we need to answer during the workshop </li></ul><ul><ul><li>How big do you think the project will be? </li></ul></ul><ul><ul><li>How many people will be involved in the product development? </li></ul></ul><ul><ul><li>At how many locations will the product be developed, tested, and deployed? </li></ul></ul><ul><ul><li>Is the product internal or external? </li></ul></ul><ul><ul><li>What are the third party tools that you will be using? </li></ul></ul><ul><ul><li>What is the development cycle of the product? </li></ul></ul><ul><ul><li>How do your current development methodologies fit into your tool plans? </li></ul></ul><ul><ul><li>Are any key roles missing from your team? </li></ul></ul><ul><ul><li>Do you have the hardware you need? </li></ul></ul><ul><ul><li>Do you have the infrastructure ready to support your plans? </li></ul></ul>
    • 23. Risk of migration <ul><li>Period of transition for the people </li></ul><ul><li>Down time </li></ul><ul><li>Duplication of effort </li></ul><ul><li>Decreased productivity </li></ul><ul><li>It's not easy to change the VOB structure after establishing a structure and locating source code into the VOBs. </li></ul><ul><li>Assigning Role/Responsibility to people </li></ul><ul><ul><li>ClearCase Administrator </li></ul></ul><ul><ul><li>Integrator </li></ul></ul><ul><ul><li>Etc. </li></ul></ul>
    • 24. Conclusion <ul><li>The migration should be plan and drive as a project </li></ul><ul><ul><li>Take more time at the beginning but it reduce the risk of failure or the rejection of change </li></ul></ul><ul><ul><li>At least one person on each role should participate in the testing </li></ul></ul><ul><ul><li>Plan a head and be prepare to perform the migration during the week-end </li></ul></ul><ul><li>ClearCase can not solve all our problem of CM </li></ul><ul><ul><li>Should look at ClearQuest for managing tickets </li></ul></ul><ul><ul><li>BuildForge may help us for the building process </li></ul></ul>
    • 25. Questions and comments
    • 26. Annex ClearCase Overview <ul><li>Very fast workspace, view, and creation. Most other tools require a complete &quot;checkout&quot; 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. </li></ul><ul><li>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 &quot;making&quot; 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. </li></ul><ul><li>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. </li></ul>
    • 27. Annex ClearCase Overview <ul><li>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. </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul>

    ×