[jira] [Commented] (INFRA-5064) bloodhound issue tracker access to local svn repository

["Gary Martin (JIRA)" <ji...@apache.org>]

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

Gary Martin commented on INFRA-5064:
------------------------------------

Perhaps I should have said this earlier. I think that the NFS solution looks like a very good idea. There may be challenges in how to trigger Bloodhound to update without direct post-commit-hook but there should be a number of ways to do the job.

Does the NFS solution look good to Infra?
                
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira