[Buildbot-devel] Dealing with / preventing "no space left on device" scenarios

Kevin Funk kevin.funk at kdab.com
Mon Mar 9 09:27:57 UTC 2015


one of our most recurring (read: boring) tasks at the moment with Buildbot is 
to make sure both the master and our slaves have enough disk space to fulfill 
their task.


For the master, I finally solved this problem by doing

  c['changeHorizon'] = 200
  c['buildHorizon'] = 100
  c['eventHorizon'] = 50
  c['logHorizon'] = 40
  c['buildCacheSize'] = 15

in master.cfg, as suggested by http://docs.buildbot.net/current/manual/cfg-global.html#horizons

Before that change, the master usually ran out of space because of the huge 
amount of pickle and log files. Now I'm wondering why these values aren't the 
default to begin with, to avoid having users run into this situation from the 


For the slaves, it's more tricky (for us).

Since the set of projects we work on is usually dynamic, builder are 
frequently renamed/added/removed. Buildbot currently does not prune no-longer-
used builder dirs, which is a problem. We usually run out of disk space on the 
slaves because of that.

I didn't find a solution to that yet, is there?

Thanks for your time

Kevin Funk | kevin.funk at kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7021 bytes
Desc: not available
URL: <http://buildbot.net/pipermail/devel/attachments/20150309/4706f942/attachment.bin>

More information about the devel mailing list