![]() |
|
|||||
|
|
|
|
|
|
|
|
CM Bridge
£1,100.00
Join Clearvision for a Webinar demonstration of CM Bridge on September 8th 2010 at 16:00 BST - Click here to Register
The CM Bridge (formally known as CC2SVN and CC2Git) Version Control Connectors provide the means to connect and replicate data bi-directionally between any of the following version control/configuration management tools;
| ClearCase | ![]() | Subversion |
| ClearCase | ![]() | Git |
| Subversion | ![]() | Subversion |
Coming soon;
Mercurial
Rational Team Concert
Accurev
Benefits
- Bi-directional bridging of Software version control solutions;
- Allows companies or departments with hybrid tool sets to share source code;
- Geographically independent, bridge version control tools regardless of location;
- Replicate whole or partial repositories;
- Control the frequency of replication;
- Ideal for gradual migration from one SCM product to another or long term synchronisation;
- Can be used as a multi-site synchronisation tool.
Description
The Clearvision CM Bridge enables complete bi-directional integration between different SCM solutions, developers can quickly and easily transport code between two version control tools.
Each Software Configuration Management (SCM) solution has different strengths and weaknesses. Hybrid multi-tool SCM environments generally exist where:
- The budget, size and requirements of a project determine the SCM solution they use;
- When separate companies are integrated as the result of a merger/takeover;
- When working in partnership with outsourced suppliers or customers.
The CM Bridge solves the challenge regarding developers who need access to code located in a different version control tool whilst maintaining all the context of the versioned history.
The Clearvision CM Bridge is the perfect solution for migration from one SCM solution to another in a controlled, staged manner (rather than a 'big bang' high risk approach).
ClearCase / Subversion & ClearCase / Git
- Changes made in ClearCase are replicated to either Subversion or Git based on a time interval;
- Commit id, date/time and checkin comments are transferred;
- Changes made in Subversion or Git are transferred to ClearCase as individual changes;
- Commit id, date/time and checkin comments are transferred;
- Commit id, date/time and checkin comments are bi-directionally transferred;
- Manages merge conflicts;
Subversion / Subversion
- Improved performance and more reliable than write through proxy;
- Changes in ClearCase are replicated to either Subversion or Git based on a time interval;
- Commit id, date/time and checkin comments are bi-directionally transferred;
- Bi-directionally transferred Subversion meta data;
- Manages merge conflicts.







