Does it really check the current disk space?

[dirk-thomas]

I do have the plugin version 0.26 installed and it reports the disk space at the beginning of the job. But the free space is equal to the size reported by Jenkins on the node page.

Looking at the slave with df -h it clearly has less free disk space by now. And after triggering a manual refresh on the Jenkins nodes page the values there update. And only after this plugin reports the correct up-to-date free disk space in new jobs.

I though the whole idea of this plugin was to not rely on the hourly refresh by Jenkins but force-refresh at the beginning of every job. I don't see how I could using this wrongly?

[dirk-thomas]

For anyone having the same problem and looking for a working solution: my Groovy script implementing this feature without a need for this plugin can be found here: https://github.com/ros-infrastructure/ros_buildfarm/blob/master/ros_buildfarm/templates/snippet/builder_system-groovy_check-free-disk-space.xml.em

[thomas-phillips-nz]

I wonder whether the existing plugin could be extended to use the real disk usage instead of using the last hourly value that Jenkins has grabbed.

Also it would be useful to be able to set free disk space per job, some of our jobs don't need a lot of disk space and can run fine when the nodes are almost at their limit, whereas other jobs need a few GB.