Hi Sean, welcome to the group!
I'm afraid I wasn't clear enough in my statement. I meant to split up the
projects, as per CruiseControl configuration - not necessarily split the
It could very well be that it's best to keep the source of the different
apps in the same repository, or workspace. But the poster says "We treat
each app as
its own project and would like to map that into CruiseControl". My point is
that if this is hard to do, perhaps they are better off switching
CruiseControl for something else, like Jenkins, Hudson, TeamCity or Bamboo.
I disagree with you on this one though:
On Sunday, May 29, 2011 4:03:42 AM UTC+2, Sean Roehnelt wrote:
> ... Git lacks good support for managing large source trees due to not
> supporting push/pull of specific repo sub-directories. My experience with
> Git shows it was created for a different set of objectives than most
> software project need to solve or are even relevant while adding a large
> amount of complexity to simple time proven methodologies like continuous
I find it a bit misleading that you say "most software projects".
You're right in that Git does not work on hierarchical data repositories of
arbitrary sizes (infinite depth). For example, if you have a global website
with web-pages for hundreds of subdivisions, each of which have their own
subdivisions, keeping it all in one Git repository would probably be a bad
idea, SVN would probably be a better option.
Now I don't think that "most projects" have this requirement. In most
projects I've seen, I check out the whole code, not some arbitrary sub-tree.
That said, Git scales really well on large repositories (the linux kernel is
a good enough example with 14 MLOCs).
Its features are practical on every software project I've seen, from tiny
open source project, to big enterprisey projects.
And it works really fine with continuous integration. Quoting the lead coder
on Jenkins <http://twitter.com/#!/kohsukekawa/status/74198251607310336>:
JenkinsCI + Git = <3
I totally agree with you on that the decision of when to split out parts of
a Git repository is a big "It depends" question, impossible for us to answer
with so little context.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at