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

Re: How to manage one project but wtih two repositories

From: Mark Breen <marklbreen_at_gmail.com>
Date: Mon, 1 Jun 2009 23:22:42 +0100

Hello Mike,
thanks for the response and the confirmation that I may be on the right
track,

I have only recently started using SVN / Tortoise, but so far, I really like
it. I am also using ANKH as a VS add-in, which seems to work well for me
also.

You mention writing a script. I will have a read about how to do it, but do
I presume that I can write a script to do the following

1) check out all code from private server
2) check out all code from public server
3) delete all code from public WC
4) copy all code from private WC to public WC
5) commit all code from newly updated public WC

the worries I have about this routine are
a) I do not like the thoughts of the mass delete, it seems a pity to ask SVN
to keep track of all of these deletes, when it may be only a handful of
files that are really getting updated.
b) how can I delete all code in the public WC anyway, surely it will also
delete the svn folders and this seems incorrect to me.

That leave the option of not actually doing the mass delete, but instead
just overwriting the files, but I really dislike that because it can leave
old unused files hanging around.

In summary, unless I do a mass delete and copy of an exported version, I am
still not sure how I can ensure I post a clean version of the private WC
code to the public site.

Have you any similar scripts that I can review, I guess if I hunt around on
the main site, or in the forums, there are plenty of samples ?

thanks for your time and attention,

Mark

2009/6/1 Mike Dixon <michael.dixon_at_denovosoftware.com>

> Mark Breen wrote:
> > I initially thought about the following steps
> >
> > 1) export all code from the working folder of the private repository
> > 2) check out all code from public site
> > 3) delete all code from working folder of public site
> > 4) paste previously exported files from step 1
> > 5) commit all files back to public site.
> >
> > This seems all wrong however, and I doubt it will work. I assume that
> there must be a better way, perhaps using branches, but I am really not sure
> what is the best way to do it.
> >
> This actually sounds about right to me. You're essentially doing a
> release, but you're uploading it to your server using Codeplex instead
> of FTP or whatever.
>
> Write a build script to do it instead of having one of your developers
> perform the steps by hand, and you're there.
>
> -Mike
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2357648
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2358487

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-02 07:01:54 CEST

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