The behavior we are seeing for some jobs is the disk usage calculation runs and is displayed in the console for every build, regardless of how much time has passed.
Running disk usage every build: that behavior seems to have been added here: https://issues.jenkins-ci.org/browse/JENKINS-10116.
But running disk usage periodically was added here: https://issues.jenkins-ci.org/browse/JENKINS-13246.
But the plugin page says “When you install this plugin disk usage is calculated each 60 minutes.” https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin
The Jenkins configuration UI exposes cron-like options for disk usage calculation of builds, jobs, and workspace, and default to value “0 */6 * * *”, which appears to intended to run every 60 minutes. We currently have the default setting.
Question: what is the intended default behavior? Every build or every 60 minutes? Every 60 minutes per job? Every 60 minutes globally?
Another behavior is after the user-created portion of the build completes but before disk usage is finished calculating, the xml api of the build returns “<result>SUCCESS</result>”, the xml api of the job returns “lastCompletedBuild” as the build that has disk usage calculating, however “lastSuccessfulBuild” and “lastStableBuild” are not updated until after the disk usage calculation is complete.
Question: when should a build be considered officially complete? Before or after the disk usage calculation? And therefore shouldn’t “lastCompletedBuild” agree with “last(un)SuccessfulBuild” and “lastStableBuild”? Or can a build be “completed” but neither successful nor unsuccessful?
Jenkins 1.596.1
disk-usage plugin 0.25
Thanks,
Jesse