Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-5064

bloodhound issue tracker access to local svn repository

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: Subversion
    • Labels:
      None

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              pctony Tony Stevenson
              Reporter:
              gjm Gary Martin
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: