[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: Subversion and CM Synergy

From: Steve Greenland <steveg_at_lsli.com>
Date: 2005-02-28 17:07:06 CET

On Mon, Feb 28, 2005 at 08:39:36AM +0200, Pasi.Havia@nokia.com wrote:
> No there won't be any CM users in our team after making the switch to
> subversion. We have CM administrators that want to have our team's
> sources in the CM anyway. That's the reason I would like to automate
> this to keep the CM in sync (almost) with our subversion sources.
> [snip]
> Why are we doing this: because CM is really a pain in the ass for us
> developers. It's awful to use and so doesn't support agile development
> where continuos integration is fundamental.
> What do we expect to be able to do with the result: use subversion
> while other teams use CM instead.

So, what you need is that your team's part of the CM repo mirror your
team's SVN repo, but it's just there for other people to look at your
current HEAD code, not for any real use. Gotcha. So the only tricky part
is matching the adds, deletes, and renames.

As someone else suggested, I suspect that the most straightforward way
is a postcommit hook, translating the SVN actions into CM actions. Yeah,
it may be more often than you need, but it will give more info to work
with than just a copy of SVN HEAD.

If that's really unacceptable for some reason, take a look at the
svn_load_dirs script. It's purpose is to help import multiple releases
of thirdparty code, comparing two directory trees and tracking file
add/deletes, which is more-or-less what you need.


"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 28 17:10:18 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.