www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5064) bloodhound issue tracker access to local svn repository
Date Tue, 07 Aug 2012 16:40:10 GMT

    [ https://issues.apache.org/jira/browse/INFRA-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430410#comment-13430410

Greg Stein commented on INFRA-5064:

svnrdump can restrict the content placed into a dump file to a specific subdirectory. All
revisions and revision properties will be carried over (even tho they might be devoid of changes),
so the revision numbering should stay consistent.

This means the target repository will still have 1.3 million revisions, but the actual content
will be MUCH smaller.

Note that svn's FSFS storage system uses a single file per revision to store the revision
properties (svn 1.8-dev has a fix for this, iirc). The actual revisions can be packed more
tightly. Daniel would know more about this. If inodes are a problem, then a BDB backend may
be more appropriate.

> bloodhound issue tracker access to local svn repository
> -------------------------------------------------------
>                 Key: INFRA-5064
>                 URL: https://issues.apache.org/jira/browse/INFRA-5064
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Gary Martin
>            Priority: Minor
> I am currently looking for possible solutions for the fact that Bloodhound requires that
it runs on the same server that any of the repositories that it tracks are located.
> I don't imagine for a second that we would be allowed to run bloodhound on the main apache
svn server and so I suspect that we are looking at whether we would be allowed to have a read
only mirror of the bloodhound area of the apache repositories using svnsync (possibly making
use of svnrdump to get the relevant part of the repository).
> Is this a feasible and sustainable solution with bloodhound currently running on bloodhound-vm.apache.org
or are there any other suggestions? 
> Many thanks,
>     Gary

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message