RE: restricting checkout???

I'm going to jump in here because this is interesting to me; how do you go about restricting access? Are you setting up each user with their own account, and then setting groups & permissions on the files, or is there a better way? How do you handle the problem of testing the code base; unit tests for each chunk works fine, but what about integration tests?

I ask because I'm about to have to setup a repository that will have the problems that you're describing; a core group of trusted developers that have access to everything, and then periodically new ones added that need to have access to their own work only, EXCEPT that there needs to be some sort of testing method so that the untrusted developers don't have to interrupt the trusted ones to run tests. The only thing I could think of was a combination of subversion + dart (http://public.kitware.com/Dart/HTML/Index.shtml), but this is by no means perfect. Any thoughts?

Thanks,
Cem Karan

-----Original Message-----
From: Lars Roland [mailto:lroland@gmail.com]
Sent: Wed 27-Apr-05 02:44 PM
To: bedouglas@earthlink.net; subversion-users
Cc:
Subject: Re: restricting checkout???

Ahh I see where you are going - you can limit the users rights to
parts of the repository - I always do this when we get a new developer
- I give him checkout access to some small subset of our entire code,
that way he can still be productive and I can be sure that he does not
run a way with all of our code.

Regards.
Lars Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 28 14:35:06 2005