On Tue, Jul 21, 2009 at 9:32 AM, Paul Butcher<[email protected]> wrote:
> I'm intrigued that nobody else seems having issues with polling?

I would want this to be optional, and not the default.  The problem
with not polling is that you can miss revisions and not build if your
CI server (or the network) happens to be down when the commit hook
happens.  This is why systems that don't support polling (like
Integrity) are a no-go for me.

As for the load on our subversion server, we had some problems when we
had dozens of CI servers hitting our SVN, but we got around that by
just increasing the polling interval on all our servers.  Even that
was just because we had an old crappy SVN server, when we upgraded our
SVN server it had no problems with the load.

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Reply via email to