"all" repository use

[nicolas de loof-2]

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 ?

[Chris van Es]

I haven't used it but do you not need to run the submodule commands?

git submodule init

git submodule update

http://git-scm.com/book/en/Git-Tools-Submodules

Chris.

On 16 October 2012 14:40, nicolas de loof <[hidden email]> wrote:

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 ?

[nicolas de loof-2]

I tried but no change

2012/10/16 Chris van Es <[hidden email]>

I haven't used it but do you not need to run the submodule commands?

git submodule init

git submodule update

http://git-scm.com/book/en/Git-Tools-Submodules

Chris.

On 16 October 2012 14:40, nicolas de loof <[hidden email]> wrote:

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 ?

[Chris van Es]

I tried to clone there and it failed with an error on the initial checkout - "warning: remote HEAD refers to nonexistent ref, unable to checkout."

Chris.

On 16 October 2012 14:56, nicolas de loof <[hidden email]> wrote:

I tried but no change

2012/10/16 Chris van Es <[hidden email]>

I haven't used it but do you not need to run the submodule commands?

git submodule init

git submodule update

http://git-scm.com/book/en/Git-Tools-Submodules

Chris.

On 16 October 2012 14:40, nicolas de loof <[hidden email]> wrote:

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 ?

[Jesse Glick-4]

On 10/16/2012 09:40 AM, nicolas de loof wrote:
> 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

It does not use submodules, and there is intentionally no master branch. It rather copies all branches from all delegates repos, prefixed by the name of the repo. See [1]
for example usage.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Grepping+all+sources

[Kohsuke Kawaguchi]

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 <[hidden email]>:
> 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

[nicolas de loof-2]

ok, seems I still have lot's to learn about git :)

2012/10/16 Kohsuke Kawaguchi <[hidden email]>

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 <[hidden email]>:

> 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

[Andrew Melo]

On Tue, Oct 16, 2012 at 12:00 PM, nicolas de loof
<[hidden email]> 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 <[hidden email]>
>>
>> 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 <[hidden email]>:
>> > 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
>
>

--
--
Andrew Melo

[Max Spring]

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
> <[hidden email]> 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 <[hidden email]>
>>>
>>> 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 <[hidden email]>:
>>>> 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]

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 <[hidden email]>:

> 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
>> <[hidden email]> 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 <[hidden email]>
>>>>
>>>>
>>>> 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 <[hidden email]>:
>>>>>
>>>>> 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

[Max Spring]

I use an "all" repository to (relatively) quickly get my hand on the sources of all plugins.
I then do find/greps to look for interesting snippets.

The long time to check out is only a first time hit.
Subsequent updates are fairly fast:

   git clone https://github.com/jyancey/jenkins-plugins.git
   real 0m1.480s

   git submodule init
   real 0m32.763s

   git submodule update
   real 43m19.027s

   git submodule update (there were no updates)
   real 0m27.481s

Instead of having a tgz you could also consolidate all sources into a single Git repository.
That would also allow for faster incremental updating.
But isn't the Git submodule approach meant to cover this?

-Max


On 10/16/2012 06:33 PM, Kohsuke Kawaguchi wrote:

> 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 <[hidden email]>:
>> 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
>>> <[hidden email]> 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 <[hidden email]>
>>>>>
>>>>>
>>>>> 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 <[hidden email]>:
>>>>>>
>>>>>> 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
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>

[Jesse Glick-4]

On 10/17/2012 01:46 PM, Max Spring wrote:
> I then do find/greps to look for interesting snippets.

The difference with all.git is that you can use git grep (without a checkout), but either can work.

> Instead of having a tgz you could also consolidate all sources into a single Git repository.

You mean, as subdirectories? You could, but then you would lose commit ID information from the original repos.