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

["Branko Čibej (JIRA)" <ji...@apache.org>]

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

Branko Čibej edited comment on INFRA-5064 at 3/29/13 5:55 PM:
--------------------------------------------------------------

I just reread Tony's comment about "you cannot use svnsync to sync a slice of a repo" and have to point out that nothing could be farther from the truth ... all we have to do is wait for the svn-1.8 release :)  Then the easiest way to do this would be to use svnsync to mirror just the BH trunk, most likely triggering the sync with svnpubsub on the target VM.
                
      was (Author: brane):
    I just reread Tony's comment about "you cannot use svnsync to sync a slice of a repo" and have to point out that nothing could be farther from the truth. :) So, indeed, the easiest way to do this would be to use svnsync to mirror just the BH trunk, most likely triggering the sync with svnpubsub on the target VM.
                  
> 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
>
> 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