If all they do is "update" to the trunk's latest revision, it could be done
taking checking out the SVN source and committing it into SVN. Care should
be taken with added/deleted files; I think there was an easy way using
¿external branches? (like 1.0.1.1).
If you need releases / tags, it only gets a bit more difficult as long as
you use releases as tags (i.e., only the copy from trunk, and no more
commits).
On Wed, Mar 30, 2011 at 19:42, SUMNER Andrew
<Andrew.SUMNER_at_customs.govt.nz>wrote:
> Our operations group require that the database scripts are in cvs, however
> the developers are using svn for everything else and it would prefer to be
> using the one tool.
>
> My eventual goal being continuous deployment into test using Jenkins (also
> would love to hear from anyone who has done this for database changes...)
>
> Andrew
>
> -----Original Message-----
> From: Thorsten Schöning [mailto:tschoening_at_am-soft.de]
> Sent: Wednesday, 30 March 2011 20:34
> To: users_at_subversion.apache.org
> Subject: Re: Sync SVN to CVS
>
> Guten Tag SUMNER Andrew,
> am Dienstag, 29. März 2011 um 21:56 schrieben Sie:
>
> > 1. Are there any tools to sync SVN to CVS? Ideally I would like
> > two way sync but I may be able to get away with one way (svn -> cvs)
> > especially if it can throw an error if the cvs file has changed.
> [...]
> > The repository I wish to sync contains database script files.
>
> And what's the purpose you need the sync for or what problem do you
> need to solve? It's unlikely that you find a tool which syncs as you
> need, but maybe one has another idea on how to solve your problem.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning
> AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
>
> Telefon: Potsdam: 0331-743881-0
> E-Mail: tschoening_at_am-soft.de
> Web: http://www.am-soft.de
>
> AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
> Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
>
> The information contained in this e-mail may be privileged and/or
> sensitive. It is intended for the addressee only and is not necessarily the
> official view or communication of the New Zealand Customs Service. If you
> are not the intended recipient you are asked to not disclose, copy, or make
> use of its contents. If received in error you are asked to destroy this
> e-mail and contact the sender immediately. Your assistance is appreciated.
>
Received on 2011-03-31 10:18:51 CEST