2009/11/2 Simon Large <simon.tortoisesvn_at_googlemail.com>:
> 2009/11/2 Richard Quadling <rquadling_at_googlemail.com>:
>> I'm a newbie to SVN, so please be gentle.
>> I'm on windows, so, please be even more gentle!
>> Using TortoiseSVN, I can manually create CSV files of the cache for
>> the repository (Right clicking a repository, choosing TortoiseSVN ->
>> Settings -> Cached Repositories -> Update & Export - more or less).
>> From there, I can create emails for each major project/branch per
>> day/week showing the commit messages and urls of changes.
>> Is there a way I can programmatically do the export? I want to have
>> the process run unattended, so no manual update & export.
>> As some indication of the project, there are 969 authors, 368,438
>> paths, 290144 revisions. It is a pretty big project.
>> I also see that I have a logcache folder containing a Repositories.dat
>> file and the cache file for the repository I'm interested in. Is this
>> file readable externally? Is the format/structure documented?
>> I've no problems accessing the CSV files to build my reports. I'd like
>> to be able to create the CSV files automatically or to update the
>> logcache file and access that.
>> Either way really.
>> Any help would be appreciated.
> You would be better off doing this on the server side, maybe triggered
> by a post-commit hook. That is how commit emails are usually sent out.
> If you use the log cache on the client you have to be sure the client
> is up-to-date first.
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\ http://tortoisesvn.net
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
No problem with doing it client side. I just want to be able to get
the logcache uptodate before I run the email scripts.
That is what I don't know how to do programmatically. I can do it
manually. But I don't want to be here every day at midnight waiting
will show the dialog for all the settings.
If this could be extended to say something like ...
tortoiseproc /command:settings /logupdate:<repository_url>
tortoiseproc /command:settings /logexport:<repository_url>
/destination:<somepath with a prefix for the exported files>
tortoiseproc /command:settings /logupdate:http://svn.xxxx.net/repository
would create ...
Something like that would be really useful for me.
Or is there another way.
The idea is that I will process the data to extract the commit logs
for all the major project branches each day and email the significant
groups. Essentially a summary of all the commits.
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-02 16:15:58 CET