On Fri, Sep 23, 2011 at 2:26 PM, Scott Smith <scottnelsonsm...@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@rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
