[Buildbot-devel] Recommendations...

Philippe McLean philippe.mclean at gmail.com
Wed Sep 21 00:22:24 UTC 2011

ease of installation,
repeatability of builds,
and cleanliness of build machines,
are priorities for me, so I use virtual machines running windows, one per
release branch.
The windows configuration only happens once, and the vm gets cloned with
each new build.
When things go wrong the vm gets trashed. Performance can be scaled in the
vm host.
Scheduling is done by buildbot.

On Tue, Sep 20, 2011 at 4:40 PM, Dan Kegel <dank at kegel.com> wrote:

> On Tue, Sep 20, 2011 at 2:59 PM, BRM <bm_witness at yahoo.com> wrote:
> > In testing the builds, I've overloaded the system a little - one build
> > failed as the build did not communicate in 1200 seconds, probably b/c I
> had
> > 12 builds running at the same time under a single slave.
> > So, what is the normal approach for divvying up builds? Do you recommend
> one
> > build-slave per processor/core? Or does it not matter so much?
> > How many builds per build slave is normal or do you expect for normal?
> I've only been running buildbot for a month; I now have four slaves
> running four different kinds of builds, triggered whenever somebody
> posts a patch for review, and also when the maintainer does his daily
> massive burst of checkins.
> My builds take long enough that I only do one build at a time on any slave.
> (OT tips: Using ccache was a big, big win.
> Presumably Incredibuild or clcache would do the same for visual studio.
> Other wins were: using ext4 instead of ext3, using an autoconf cache,
> and, especially for amd processors, using cpufreq-set -g performance.)
> - Dan
> ------------------------------------------------------------------------------
> 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. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110920/c0178321/attachment.html>

More information about the devel mailing list