found the doc: seems interesting any live example to show? or a demo on skins, for example, ie not much submodules, so it seems a good cancidate for tests
Regards, Hervé Le vendredi 14 février 2014 08:46:32 Baptiste Mathus a écrit : > +1 on the submodule solution. We started using it some months ago since the > branch option came out. > As a simplistic analogy, you can see it as svn: externals equivalent. > > It helps developers (and ci configuration) to retrieve many related > projects in only one clone command. > > My 2 cents > > Le 14 févr. 2014 05:10, "Mark Derricutt" <m...@talios.com> a écrit : > > Jenkins could build from a super-repo that uses git submodule. > > > > Since a quite a few versions ago, git-submodules can now follow a branch > > rather than a fixed SHA1. > > > > So you could build/test monolithically, branch/commit individually. > > > > Compromise maybe? > > > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote: > > each entry would mean 1 git repo + 1Jenkins job (or even more, since > > > >> plugins > >> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for > >> Maven > >> 3.1.x) > >> IMHO, we're not ready for such granularity, neither at git nor Jenkins > >> level > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
