Install post-build-task plugin and use that to clean the workspace at the end of the build.
-- Sami Pawel <pgronkiew...@gmail.com> kirjoitti 18.2.2013 kello 13.01: > Hi, > > I have a problem with jobs being started on a slaves that are low on disk > space. I know there is a setting to turn the slaves offline automatically > when disk space falls behind a certain threshold, but it isn't reliable > enough. I think the problem may be with how often the check is performed (as > it can take up to an hour to turn the slave back online automatically after > freeing up enough disk space). The problem in my situation is when I have > big load on my slaves (many jobs and long queue). I have a job running on a > slave X which makes it get low on disk space. After the job finishes the > slaves doesn't get turned off automatically though - new jobs get assigned > to this node and are started, but fail with "no space left on device" error > message just a while later. Jenkins assigns all fitting jobs from the queue > this way, resulting in multiple failures, before node gets turned offline. > Is there any way to prevent this behavior? > > > > -- > View this message in context: > http://jenkins.361315.n4.nabble.com/Jobs-starting-on-slaves-with-no-disk-space-tp4656054.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
