[Cruisecontrolrb-users] My continuous integration server is hitting git too hard

7 views
Skip to first unread message

Scott Smith

unread,
Sep 23, 2011, 5:26:12 PM9/23/11
to cruisecont...@rubyforge.org, Forrest Chang
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)

Chad Woolley

unread,
Sep 23, 2011, 5:36:54 PM9/23/11
to cruisecont...@rubyforge.org, Forrest Chang
On Fri, Sep 23, 2011 at 2:26 PM, Scott Smith <scottnel...@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
Cruisecont...@rubyforge.org
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Scott Smith

unread,
Sep 23, 2011, 7:46:26 PM9/23/11
to cruisecont...@rubyforge.org, Forrest Chang
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.
Reply all
Reply to author
Forward
0 new messages