Re: jenkins and git repository monitoring

Patrick Gerken <do3ccqrv-gM/[email protected]> Sun, 20 Nov 2011 16:59:28 +0100
Newsgroups gmane.comp.web.zope.plone.devel,gmane.comp.web.zope.plone.website
Message-ID <CAFefbnGpSy8ASgENdt_HXQX=QLODeCpgbuLNZZFcbFrypVGf7w@mail.gmail.com>
On Sun, Nov 20, 2011 at 15:51, Timo Stollenwerk <[email protected]> wrote:
> Hi Patrick,
>
> I'm not sure if polling github is really what we want for CI (the
> ScriptTrigger plugin does poll after all if I understand it correctly).
> Polling works fine for smaller projects, but I don't think it does
> really scale for a project like Plone. With a large number of jobs
> polling this is a waste of network resources and we don't really get
> atomic commits (which is not really CI then).

Yes, it's really slow, right now it takes 20 minutes. We are polling
github and svn right now, and the git plugin is too stupid to work
with multiple checkouts reliably, and believes every time something
has changed.

My idea would be a small improvement of the current situation, while
yours below certainly is better, but it needs to be done.
I'd love to join the efforts, but right now I can't even keep up with
mail traffic :-(

Best regards,

   Patrick

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d