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

Re: Using a shared WC on a network drive

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-07-31 05:07:04 CEST

On 7/30/06, Chris Ormerod <chris.ormerod@ruralpress.com> wrote:
> Apart from the obvious "social" problem as described in the last paragraph
> of this message by Simon Large:
> http://svn.haxx.se/tsvnusers/archive-2006-06/0023.shtml (i.e. someday
> somebody will overwrite a file in the WC at the same time as somebody else),
> are there any technical issues related to sharing a SVN repository in this
> way?
>
> Following a dramatic start to our first ASP.Net project (a *lot* of code was
> accidentally overwritten while they were working locally and copying to dev
> for testing), I managed to convince the other devs here to give SVN a go, it
> worked brilliantly and we have been using SVN for the SQL scripts, ASP.Net
> sites and .Net applications we develop for just on a year and it is working
> fine.
>
> Now that SVN has proved itself we want to now add our ASP classic sites to
> SVN - at the moment these are worked on directly on the dev server either
> via FTP or shared drive access. So obviously we already have the problem of
> people overwriting other peoples work, but at least using SVN will give us
> the ability to at least go back and see what the other persons work was.
>
> We have tested using TSVN on a networked WC and it *seems* to work fine and
> from the research I have done on the net I actually haven't found any
> references to "Using a networked WC screwed up my source code". So I thought
> I would just check here to be sure.

Doing this is generally discouraged. You really aren't too far from a
non-SVN "solution" here - If I have an editor that doesn't check for
updates on a file before saving, it's really, really easy to clobber
another developer's work, and unless things were checked in, you
*can't* go back and look. You aren't saving yourself much here.

Honestly, if you're going to share a WC amongst developers, I don't
see much of a reason to spend the time and resources setting up an SVN
server & repository.

Why does everyone have to work off the same networked WC? At a
previous job, we had both classic ASP and .NET projects, and
*everyone* had a local copy to work with, even before we started using
source control. No one ever worked on a shared copy of anything.

> As a discussion point, how do others work on ASP classic (or PHP etc) sites
> and manage to merge SVN into the workflow?

I manage a JSP/servlet web application, and SVN isn't "merged into the
workflow" - SVN *is* the workflow. If a file isn't in SVN, it isn't
in the application. No code is edited outside the developer's
sandbox. Builds are deployed from SVN into the various server
environments, and it's a one-way street - things go from SVN out to
the servers, and never from the servers back into SVN. All changes
must originate with the developer and go through the stages in SVN.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Jul 31 05:07:17 2006

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