Les Mikesell wrote: > On Fri, May 10, 2013 at 12:38 PM, JonathanRRogers > <[email protected]> wrote: >> Jenkins' git plugin performs poorly with hundreds of branches in a single >> repository. I haven't tried it with hundreds of repositories, but I wouldn't >> be surprised if that also performed poorly. I now avoid the git plugin >> entirely and use git commands directly. > Do you know if this is specific to git or is it just the nature of > polling for a whole bunch of different jobs on the same time cycle? > Or perhaps made worse by polling the same repository with many jobs at > the same time?
The problem is with Jenkins' git plugin. When I configured it to poll a repository without limiting branches (the default configuration), one Jenkins thread would use 100% of a CPU for many minutes just to figure out what jobs to trigger. No git operations take anywhere close to that when using the native commands. -- Jonathan Rogers -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
