Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Message-ID: <1475500358.25858.38.camel@apache.org>
Subject: Re: Handling a large number of git repositories for a project
From: Robert Munteanu <rombert@apache.org>
To: infrastructure-dev@apache.org
Date: Mon, 03 Oct 2016 16:12:38 +0300
In-Reply-To: <47956b55-a9e9-763f-3f65-2a27ebf4879b@apache.org>
References: <1475499292.25858.35.camel@apache.org>
	 <47956b55-a9e9-763f-3f65-2a27ebf4879b@apache.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
archived-at: Mon, 03 Oct 2016 13:12:43 -0000

On Mon, 2016-10-03 at 14:57 +0200, Daniel Gruno wrote:
> If you use https://reporeq.apache.org/ and manage the import of data
> yourself, you won't be burdening infra much :)

Ah, that looks nice.

Are repositories automatically created or is there a manual step
involved?

I'm trying to understand if we need an intermediate catch-all
repository where we store new modules before a git repository is
created.

Thanks,

Robert

> 
> With regards,
> Daniel.
> On 10/03/2016 02:54 PM, Robert Munteanu wrote:
> > Hi,
> > 
> > In the Apache Sling project we're considering moving from SVN to
> > Git
> > [1].
> > 
> > We believe that having a large number of modules in the same git
> > repository would be counterproductive and missing the point of git,
> > so
> > we would like to create 1 git repository per module.
> > 
> > This has two main implications:
> > 
> > 1. When migrating we would need to create ~300 modules in git
> > 2. Periodically we would create new repositories, since new module
> > contributions would also end up in new repositories
> > 
> > Although other projects seem to have more than one repository, I
> > could
> > not find one with more than 100. So before we start down a road
> > which
> > can prove troublesome, I'd like to ask
> > 
> > 1. Is creating a large number of modules in git for a single
> > project
> > problematic by itself?
> > 
> > 2. What ways do we have of making sure that infra is not burdened
> > by
> > our rate of repo creation? We would of course welcome options that
> > would allow us to manage the repos ourselves, but anything that
> > makes
> > sure infra is not impacted by our activity is welcome.
> > 
> > Thanks,
> > 
> > Robert
> > 
> > [1]: http://markmail.org/message/kvhmn7kghvh7lual
> > 
> 
> 
>