You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Tony Stevenson (JIRA)" <ji...@apache.org> on 2012/08/07 15:33:10 UTC
[jira] [Updated] (INFRA-5064) bloodhound issue tracker access to
local svn repository
[ https://issues.apache.org/jira/browse/INFRA-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson updated INFRA-5064:
----------------------------------
Status: Waiting for Infra (was: Waiting for user)
> 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