|
It really comes down to how big your
project is, and how it can be built and used by your community.
Anything that is core to the project should probably be in the
same repo. Anything note core, could be moved into separate
repos.
One reason to split things up is if you don't need to build
everything together.
Not having everything together gives you some added flexibility
with your builds, but it also adds complication which your project
and community may not need.
Dave
On 07/30/2012 12:35 PM, Matthew Heitz wrote:
Thanks Eric. That
solution had occurred
to me but I'm not thrilled about the additional complexity.
Can somebody tell me the benefit
of
having many Git repositories vs. just one? My team was working
just
fine with only one CVS repository.
-Matt
--------------
Matt Heitz
Developer, Eclipse EGL Development Tools and IBM Rational
Business Developer
http://www.eclipse.org/edt/
http://www.ibm.com/developerworks/rational/products/rbde/
From:
Eric Gwin
<eric.gwin@xxxxxxxxxx>
To:
"Git related
discussions,
specifcally migration help for projects
at Eclipse.org" <git@xxxxxxxxxxx>,
Date:
07/30/2012 11:25 AM
Subject:
Re: [git] configuring
Hudson build job for multiple Git repositories
Sent by:
git-bounces@xxxxxxxxxxx
As I understand it, there'd be a separate build job
for
each repo. The Jobs should rely upon each other in the needed
build order
using "spawn another build" or "start after X project".
Then the base build kicks off, spawning higher level projects
(from
a dependency point of view) as it goes.
That's the theory anyway. I'm not sure what other teams do, and
I haven't
gotten to the point of splitting the builds yet (we needed to
maintain
all history, so I pretty much fully migrated from svn to Git
(1->1),
and will be pruning and adding additional repos shortly.
I did do some experimenting though and linking builds seems to
work ok.
Though I haven't yet figured out how to share workspaces (so
test can directly
access the built artifact for instance).
HTH
Eric
On 30/07/2012 10:49 AM, Matthew Heitz wrote:
Hi,
I need some help configuring Hudson to build my project after
its migration
from CVS to Git.
We migrated from one CVS repository to several Git repositories,
thanks
to statements like "Typically, one Git repository (.git) is
created
for each logical unit, or grouping of code -- a plugin, a
connector, a
component, and so on." in http://wiki.eclipse.org/Git/Migrating_to_Git
. I want the code from all of the Git repos to be compiled
together
by one Hudson job, but I haven't succeeded yet.
Hudson's build config page allows you to specify as many Git
repos as you'd
like, but I just read in the Hudson Book http://wiki.eclipse.org/The_Hudson_Book
that "Providing multiple repositories only makes sense when they
are
clones or instances off the same repository, since they will be
used for
merging together the content prior to the build." That's not
what I'm trying to do. Each repository contains a distinct set
of
plugins.
In order for my build to work, the files from all repos must be
extracted
to the same directory in the Hudson workspace. But Hudson is
removing
the previous contents of the directory each time it fetches
files from
a repo. I end up with only the files from the last repo.
I tried telling Hudson to put each repo's files into a different
place,
but then javac couldn't find them.
I appreciate any help you can give me.
-Matt
--------------
Matt Heitz
Developer, Eclipse EGL Development Tools and IBM Rational
Business Developer
http://www.eclipse.org/edt/
http://www.ibm.com/developerworks/rational/products/rbde/
_______________________________________________
git mailing list
git@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/git
_______________________________________________
git mailing list
git@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/git
_______________________________________________
git mailing list
git@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/git
|
