Subversion connector for IBM Rational ClearCase

On the 30th of May we did another “Subversion in the Enterprise Webinar”. Quite a few people asked about migrating from ClearCase® to Subversion (Bob blogged about that already) and some asked specifically about synchronizing the two systems. For example:

“I work for a place that does contract development. Often we find people that are deeply entrenched with ClearCase, which works fine as long as you are working within the local environment. Is there a tool set that allows moving to and from Clear Case? We far and away prefer to work with Subversion, and only push back major releases to the customer’s ClearCase repository.”

There is a solution for this: you can download a ClearCase <> Subversion connector right here from openCollabNet, for free!

The connector synchronizes changes between IBM Rational ClearCase and a Subversion working copy. It provides two modes to synchronize data: from ClearCase to Subversion, and vice versa.

From ClearCase to Subversion: For the connector to work in this mode, you need to have two ClearCase views to clearly distinguish between modifications made:

  • A “ClearCase Reference View” which must match the Subversion working copy.
  • A ClearCase Current View” containing the most recent changes made to the ClearCase VOB.

The connector gets the difference between a ClearCase – Reference View and the ClearCase – Current View, and synchronizes it with the Subversion working copy.

When you export, the following will happen:

  • The connector will detect the difference in data between the two ClearCase views.
  • The file deleted (red), file added (blue) and file renamed (green) will be exported to the Subversion working copy and also directly committed to the Subversion repository.
  • The file whose content has been modified (Orange) will be updated only to the Subversion working copy. You need to manually commit it to a Subversion repository to synchronize all data.

From Subversion to ClearCase: In this mode, the connector brings in the changes made in the CollabNet Subversion working copy to a ClearCase view of your choice.


When you import, the following will happen: The file deleted (red), directory added (blue), file renamed (green) and file whose content is modified (orange) in the Subversion working copy will be imported to the ClearCase view. You need to manually checkin the changes made in this view to the ClearCase VOB.

The connector can be used with stand-alone Subversion as well as with CollabNet Enterprise Edition and SourceForge Enterprise Edition. If you want more information about the connector, download it and read the included manual (most of the above is from there). To get community support for the connector, go to our connectors project on openCollabNet. Support is also available directly from CollabNet.

Next to the ClearCase connector we have two free connectors for HP Quality Center. Our Subversion connector allows you to version test plans in Subversion and the CollabNet Enterprise Edition connector bi-directionally synchronizes defect information to ensure that developers and testers work on the same data. You can download datasheets for all connectors from our corporate web site.

Tagged with: , , ,
Posted in Subversion
12 comments on “Subversion connector for IBM Rational ClearCase
  1. Alexander Wolfson says:

    How to get the Linux Version of the subversion connector?

  2. Karthi Swaminathan says:

    Hi Alexander Wolfson,
    Our connector works with Subversion installed on Windows or Linux and ClearCase installed on Windows. The connector is installed on the same Windows server where ClearCase is installed. At present, we do not support a version of the connector that can run on Linux. — Karthi

  3. Ken Wood says:

    The manual for the connector says the opposite – it says “To install and
    configure this connector on a linux platform contact the CollabNet Services
    Team” – sure sounds to me that you have a linux version, I just can’t figure
    out how to contact the “CollabNet Services Team” to get a copy…

  4. Ken Wood says:

    The manual for the connector says the opposite – it says “To install and
    configure this connector on a linux platform contact the CollabNet Services
    Team” – sure sounds to me that you have a linux version, I just can’t figure
    out how to contact the “CollabNet Services Team” to get a copy…

  5. Karthi Swaminathan says:

    Hi Ken,
    Thanks for pointing out the discrepancy in the manual. We will update it. Our earlier version of ClearCase connector had a linux version. It was more of a custom install/configuration script. But we no longer support that.
    You can contact our support department at http://www.collab.net/support/index.html and services department at http://www.collab.net/about/contactus/

  6. Juan Venegas says:

    Hi,
    When I am trying to import from svn to cc, i am getting the following error:
    ERROR: The working copy either has local modifications or is a mixed revision working copy.
    Suggestions?
    I don’t have local modifications…what is mixed revisions?
    Juan

  7. Alexander Thomas says:

    Juan,
    Its because your Subversion working copy is under mixed revision. Do a svn update on the root of your subversion working copy, then run clearsvn import again.
    Juan, plz use the clearsvn discussion forum for any further clarification.
    http://connectors.open.collab.net/ds/viewForumSummary.do?dsForumId=40
    thanks

  8. kriz says:

    Can i use this connector with the ClearCase Remote Client? remote client requires adding credentials for every command but connector does not expose that functionality
    Regards!

  9. Gopinath Velayudhan says:

    Hi,
    I am testing the connector using Version 1.1. would like to know if the connector works with Dynamic views. I am trying to update a Clearcase dynamic view it identifies the update in SVN but does not udpate it in ClearCase.
    C:>C:CollabNet_Subversion_ServerSVN_CC_Connectordistclearsvn import -s C:svn_workProject2componentshardware -t svn://localhost/Project2/trunk/components/hardware -c X:gvelayud_V2ETS_CM_TEST
    componentshardware -r 17:18
    —- Change List output follows this line —-
    —- End of Change List output —-
    UPDATE of X:gvelayud_V2ETS_CM_TESTcomponentshardwareaddingfileinSVN.txt from C:svn_workProject2componentshardwareaddingfileinSVN.txt
    All OK!
    (no errors or warnings or rmnames)
    thanks in advance.

  10. Gopinath Velayudhan says:

    Update– i see that the updates made to a files are being synced with ClearCase dynamic view (though the files have to be checked in manually). This Syn does not work with files that are added or deleted from SVN worspace. I get the following message when running the command
    C:>C:CollabNet_Subversion_ServerSVN_CC_Connectordistclearsvn import -s C:svn_workProject2componentshardware -t svn://localhost/Project2/trunk/components/hardware -c X:gvelayud_V2ETS_CM_TEST
    componentshardware -r 15:21
    —- Change List output follows this line —-
    —- End of Change List output —-
    The Directory Comparison Yields:
    —————————————–
    WARNING: there are files to be added as follows
    anotherfile.txt
    WARNING: there are files to be removed as follows
    another_file.txt
    No file changes to update.
    TOTAL ERRORS ….. 0
    TOTAL WARNINGS … 2
    TOTAL RMNAMES …. 0

  11. To perform either comfortably, you don’t need to have to possess the literary sensibility of terrific authors, but you do involve to do particular things, a few of which we will consider it inside approaching paragraphs. Usually, regardless of what I do, I all feel twice of them.

  12. MANISH KUMAR says:

    Hi,

    I am getting error “Pathname is not within VOB” whenever I try to run the clearsvn export command.

    I have One Dynamic View i.e. view1 and another dynamic view i.e. view2 as reference and I have local working copy of Subversion also.

    my export command was like
    “Clearsvn export -b “Reference view directoty” -c “current view directory” -s “SVN Working directory” -l “logfilename”

    Anyone here can help to resolve the issue.

    Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

*