how to keep track of svn checkouts by the users

[abhijit vaidya <ab...@gmail.com>]

Hi,

I am subscribed user of this mailing list. And I just need one help from you
guys.

I am using subversion version control system form last one year with lot of
repositories. We have many users to access it who use to keep update the
revisions, checkouts, commit,export etc etc

I have following questions,

1) How to know how many users checking out the respositories?
2) How to know about all the checkouted repositories are committed
completely or no?

is SVN hook is helpfull regarding it? if it is, can you please help me with
configuration of it so that it will send a mail to system administrator with
all the above reports.

Please get back to me ASAP

Regards
Abhijit

Re: how to keep track of svn checkouts by the users

[Ryan Schmidt <su...@ryandesign.com>]

On Sep 12, 2008, at 06:41, John Peacock wrote:

> Please don't use svn@subversion.tigris.org as a list address; that  
> is strictly used for commit messages from the project itself, not  
> for questions.
>
> abhijit vaidya wrote:
>> 1) How to know how many users checking out the respositories?
>> 2) How to know about all the checkouted repositories are committed  
>> completely or no?
>
> Subversion is a client/server application.  There is no tight  
> connection between the server and the client, but only between the  
> client and the server.  By this I mean that there is no way from  
> the server to "ask" the client if its working copies are up to  
> date.  When clients check out any portion of the repository, that  
> working copy is the only evidence that this has happened.  And  
> indeed, the end user could just as easily check out some part of  
> the repo and then immediately delete the working copy and the  
> server will have no way of "knowing" that.
>
> You might be able to glean some statistical information from the  
> Apache logs (if you are running Apache) about the number of unique  
> client interactions over any given time span.  But that is about  
> it; you won't even be able to get any useful data about what paths  
> were checked out (since that information is part of the DAV  
> communication that is not logged).

You can write a post-checkout hook to do whatever you want when  
someone checks out from your repository. That's going to be the  
extent of what you can do, though. As John said, the server cannot  
know whether users have uncommitted changes in working copies.

Subversion does not have a post-checkout hook, but you can fake it  
using my svnhookdispatcher script, provided you're serving your  
repository using Apache and not svnserve:

http://www.ryandesign.com/svnhookdispatcher/



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: how to keep track of svn checkouts by the users

[John Peacock <jo...@havurah-software.org>]

Please don't use svn@subversion.tigris.org as a list address; that is strictly 
used for commit messages from the project itself, not for questions.

abhijit vaidya wrote:
> 1) How to know how many users checking out the respositories?
> 2) How to know about all the checkouted repositories are committed 
> completely or no?

Subversion is a client/server application.  There is no tight connection between 
the server and the client, but only between the client and the server.  By this 
I mean that there is no way from the server to "ask" the client if its working 
copies are up to date.  When clients check out any portion of the repository, 
that working copy is the only evidence that this has happened.  And indeed, the 
end user could just as easily check out some part of the repo and then 
immediately delete the working copy and the server will have no way of "knowing" 
that.

You might be able to glean some statistical information from the Apache logs (if 
you are running Apache) about the number of unique client interactions over any 
given time span.  But that is about it; you won't even be able to get any useful 
data about what paths were checked out (since that information is part of the 
DAV communication that is not logged).

It sounds like you want to have something like Perforce, where each client has 
to register with the server what it is checking out.

Sorry

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org