Aborted Jenkins ISO builds can cause next ones on the same isobuilder to fail
E.g.
https://jenkins.tails.boum.org/job/build_Tails_ISO_bugfix-12529-simplify-kernel-install-in-vagrant/5/
left 14G of data behind itself in
/var/lib/jenkins/workspace/build_Tails_ISO_bugfix-12529-simplify-kernel-install-in-vagrant/vagrant/,
which broke the next ISO build on that isobuilder. I had to manually
clean this up to repair that isobuilder.
How about we delete
/var/lib/jenkins/workspace/build_Tails_ISO_*/vagrant/ (possibly
excluding the currently running job’s directory) at some relevant time,
e.g. before building? There might be a more clever solution though, I’ll
let you think about it :)
Feature Branch: puppet-tails:bugfix/12577-cleanup-failed-build-leftovers
Parent Task: #12531 (closed)
Original created by @intrigeri on 12577 (Redmine)