"Silverman, Josh" <Josh.Silverman_at_ngc.com> wrote on 05/12/2008 01:12:26 PM:
> This issue comes up among us because we are using Subversion internally
> but have to transfer our source files to a ClearCase repository used by
> several related projects maintained by a different organization.
>
> Transferring files from ClearCase to Subversion is relatively painless.
> We dump the entirety of the VOBs from ClearCase into a working copy and
> let Subversion sort out the changes. (While simple to perform, it is
> not clear how to spot whether file are missed during the transfer. This
> is not the main issue, but it is a running concern.)
>
> However, merging code from Subversion to ClearCase is another problem
> entirely. Currently we run a "diff" of the two repositories using the
> Beyond Compare. We have to tweak Beyond Compare a bit to account for
> the meta-data issues, but eventually we get a list of conflicting and
> orphaned files. We then check out each individual file change and copy
> each new file from Subversion into ClearCase, and manually add those
> files and directories into source control. For each VOB in ClearCase,
> we copy all conflicting files from Subversion, overwriting the existing
> versions in ClearCase. This is a very cumbersome process for an update
> that may involve no more than 10 or 12 file changes. Is there any way
> that we can simply dump the Subversion changes into ClearCase? Is
> there, for example, a tool that can be used that can facilitate
> communication between the two tools? I realize that this primarily a
> ClearCase issue -- it is an extremely unfriendly tool -- but I was
> wondering if the Subversion group had any experience with this.
There is a (two-way) connector between ClearCase and Subversion on
CollabNet:
http://www.collab.net/servlets/OCNDirector?id=CIPCSVNIBMCC
It has served us well many times.
- Nico
Received on 2008-05-12 13:32:50 CEST