On 24 April 2012 12:48, Eugene Sajine <euguess@xxxxxxxxx> wrote: > We are working in the environment where we have hundreds (700 + and > counting) or projects with many of them reused by others. > We are following strictly one project = one repo rule without any > subtrees or submodules. > What you are asking about is "integration" and IMHO has nothing to do > with git - i.e. should be VCS independent. > We are using integration on the artifact level and it works amazingly well. > But we also use pretty strict naming and location convention that > allows us to script around the whole setup very easily. > > In order to track dependencies between projects we use Ivy. > The project can be compiled locally using local copies of the upstream > project artifacts built by developer on the same machine or if not > present, the current production artifacts are used. > We also have Jenkins CI server that helps with integration. It is very > simple and straight forward set up without any unnecessary > complications IMHO. > Feel free to contact me if you need more info about such set up. So how do you handle implementing features/changes that involve more than one project? Surely, you do not manually create topic branches in each of the involved repos? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html