|
Hi,
I think I know what is the problem. If you use share workspace and it is big (there is a lot of other stuff then only particular job workspace), it could try to calculate size for all files and subfiles - it can take a lot of time. Disk usage is called by listener after all build steps are finished and result is set (failed disk usage does not mean that build should change its result). But it is strange that build history shows that build is finished, because it should not be in state completed. I will try to reproduce this issue, but with disk-usage 0.26 and Jenkins 1.580 which are current used versions.
You can check if disk-usage perform calculation in build log, there should be info message that calculation is in progress.
|
