verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
vmeson has quit [Ping timeout: 246 seconds]
vmeson has joined #buildbot
zware has quit [Ping timeout: 244 seconds]
zware has joined #buildbot
mjw has joined #buildbot
wielaard has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))]
wielaard is now known as mjw
mark_ has joined #buildbot
_hc[m] has joined #buildbot
<_hc[m]> hey all, thanks for buildbot! I'm in the process of converting F-Droid to use buildbot, then we can ditch our custom code.
<_hc[m]> we want each build to happen in a fresh libvirt VM, so I'm wondering how to best structure this in the buildbot setup
mark_ has quit [Ping timeout: 256 seconds]
<_hc[m]> right I was looking at that. It seems that `base_image` will be copied to `hd_image` on each run. We have big base images, like 10GB. Is there a way to use snapshots or something like that?
mjw has quit [Quit: Leaving]
<glogan> I'm not familiar with using libvirt directly, but https://docs.buildbot.net/latest/manual/configuration/workers-libvirt.html#configuring-master-to-use-libvirt-on-remote-server looks like it's got a hookscript where you can customize behaviour
<glogan> I'd imagine the same logic would work on a local loopback approach if you've only got one node.
<glogan> If that doesn't work it might be worth mailing the list. I'm just a user :)
<_hc[m]> thanks for your help :)
alicef has quit [Quit: install gentoo]
alicef has joined #buildbot
mjw has joined #buildbot
mjw has quit [Remote host closed the connection]
mjw has joined #buildbot
mjw has quit [Remote host closed the connection]
mjw has joined #buildbot
mjw has quit [Quit: Leaving]