Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We use TortoiseSVN + VisualSVN and we have a system we'd like to get under version control, and I'm trying to figure out the best way to set it up. Unfortunately code edits do occur directly in the production environment (I'd like to move away from this practice but it would require some major system changes so it's not something I can change today) so I need to consider the production code base as a working copy and multiple users need to be able to commit to the repository from that working copy. How do I set it up so that multiple users to share a working copy?

Users login information is stored in the .svn folders so I get an error when a different users attempts to commit a change using a working copy that I checked out. On an older version of subversion (several years ago) I was using svn+ssh and I was able to remove user specific information from the svn+ssh command so that it worked for anyone (since each user had auto-username set in putty). But now I see that subversion uses a non-text format so I can't remove information of the user that checked it out.

Although I have a preference for subversion (our users already know it) I'd be open to hear if a similar setup is possible or would work better on alternative solutions (git, mercurial, etc.) as long as there is a plugin for Visual Studio similar to VisualSVN.

Thanks.

share|improve this question
    
I don't fully understand your question. Are you saying you want to have multiple users to edit a checked out working copy of an svn source tree? That sounds like a backwards thing because it's one of the things source control tries to prevent. –  aseq Mar 9 '12 at 23:03
2  
If you mean you currently have people working on a physical source tree and you want to move that source tree into subversion because it is not under source control yet then I'd say do that ASAP. The current scenario is asking for disaster. It's not that hard actually... –  aseq Mar 9 '12 at 23:06
    
What I'd like is for multiple users to be able to use tortoisesvn but they'd all be using the same working copy. I know it's not ideal but it will be awhile before I can get to a position where edits aren't occurring directly on the production code base. At the very least I'd like to start by getting it under revision control. –  Benjamin Bryan Mar 10 '12 at 0:09
    
I envision a poor windows server with a checked out copy of your source, which is the production copy where people log into the box and directly edit the source. If your situation is something like that I can not advice you anything but to forbid anyone from doing that at all, ever. Be a BOFH (bastard operator from hell) because if you're not it will only end in disaster. I also can't really imagine a situation where it is impossible to move to revision control right away. You rather wait for things to go bad first? –  aseq Mar 10 '12 at 0:25
    
Why you used single user in svn+ssh repo and removed this data from repo? Please explain. Or use single ssh user for all developers now –  Lazy Badger Mar 10 '12 at 9:29
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.