Cruisecontrolrb users - Sep 2011 - My continuous integration server is hitting git too hard

We have been rapidly expanding our use of CruiseControl.rb into new projects
and new test metaphors:

   - 13 Cruise Control projects, against several repositories on unfuddle, a
   commercial git host provider.
   - One of the repositories is hit by 6 of the projects.  I.e., every time
   the repository is updated, 6 cruise control projects simultaneously fetch
   from the repository.

Needless to say, unfuddle was unhappy with the resulting load and has
requested that we "cut it out".

I''d like to continue to run the 6 projects in parallel.  One way to do
this
would to be have one of the 6 projects do the unfuddle fetch, then have its
code set copied to the other 5.

My question is: has anyone else encountered this problem (and, even better
yet, solved it)?

Thanks in advance,

Scott Smith - Q/A Software Engineer

-- 
Scott Smith

http://twitter.com/_ofd (OldFartDeveloper)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20110923/fd030119/attachment.html>

On Fri, Sep 23, 2011 at 2:26 PM, Scott Smith <scottnelsonsmith at
gmail.com> wrote:
> Needless to say, unfuddle was unhappy with the resulting load and has
> requested that we "cut it out".
> My question is: has anyone else encountered this problem (and, even better
> yet, solved it)?
Serialize your builds. Which would probably suck for you, since they
are working fine in parallel.  Or better yet, use a Git hosting
provider that can handle the load.  I doubt GitHub would complain
about this, but I could be wrong.  You can always hit your own fork
running on a server you own.

-- Chad

Thanks, Chad.

Your idea of "hitting your own fork" didn''t occur to me but
actually sounds
like the best solution.  Great idea!

Thanks.  When I get it going, I''ll write up what I did; I''m
sure others have
run into the same situation.

Scott

I AM serializing some of the other projects to get the load down.

On Fri, Sep 23, 2011 at 2:36 PM, Chad Woolley <thewoolleyman at
gmail.com>wrote:
> On Fri, Sep 23, 2011 at 2:26 PM, Scott Smith <scottnelsonsmith at
gmail.com>
> wrote:
> > Needless to say, unfuddle was unhappy with the resulting load and has
> > requested that we "cut it out".
> > My question is: has anyone else encountered this problem (and, even
> better
> > yet, solved it)?
>
> Serialize your builds. Which would probably suck for you, since they
> are working fine in parallel.  Or better yet, use a Git hosting
> provider that can handle the load.  I doubt GitHub would complain
> about this, but I could be wrong.  You can always hit your own fork
> running on a server you own.
>
> -- Chad
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>


-- 
Scott Smith

http://twitter.com/_ofd (OldFartDeveloper)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20110923/afaa0a13/attachment.html>