Ah, interesting. If this is something people want, we can get this automatically updated, too.
But I don't think this works for what I needed the all repository originally for, which is searching across histories of plugins, computing statistics about commits, etc. (git grep, git log -S, git rev-list.) I also suspect it'll take forever to check out, because it'd update one repository at a time. Maybe what would be useful is to have the tgz archive of the latest source tree from all the plugins? This will let people do "grep -r". I guess "what are you trying to use this repository for?" is what I'm getting at. 2012/10/16 Max Spring <[email protected]>: > A coworker of mine saw this and put this on GitHub > https://github.com/jyancey/jenkins-plugins > > It uses proper Git submodules for each plugin. > > git clone https://github.com/jyancey/jenkins-plugins.git > cd jenkins-plugins > > git submodule init > git submodule update > > -Max > > > > On 10/16/2012 10:02 AM, Andrew Melo wrote: >> >> On Tue, Oct 16, 2012 at 12:00 PM, nicolas de loof >> <[email protected]> wrote: >>> >>> ok, seems I still have lot's to learn about git :) >> >> >> Well, in fairness, that's a pretty arcane usage of git, so I wouldn't >> feel too bad :) >> >>> >>> >>> 2012/10/16 Kohsuke Kawaguchi <[email protected]> >>>> >>>> >>>> Think of it as the union of all the repositories. There's no 'master' >>>> branch in it --- it has all the refs from all the repositories. >>>> >>>> See https://wiki.jenkins-ci.org/display/JENKINS/Grepping+all+sources >>>> for example. >>>> >>>> 2012/10/16 nicolas de loof <[email protected]>: >>>>> >>>>> Hi, >>>>> >>>>> I wonder how to use the http://git.jenkins-ci.org/all.git repository >>>>> I cloned it, and expected it to have all jenkins repos as submodules, >>>>> but >>>>> this is not the case and I get an empty working copy, so wonder how you >>>>> use >>>>> it ? >>>> >>>> >>>> >>>> >>>> -- >>>> Kohsuke Kawaguchi >>> >>> >>> >> >> >> > -- Kohsuke Kawaguchi
