|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I have encountered this issue on my Jenkins installation with a subset of the jobs.
The jobs that have this problem are the ones that have a Custom Workspace defined.
After the job finishes, the jenkins process on the master starts using a lot of CPU while the Disk Usage plugin is trying to estimate the size of the workspace on the slave.
While this is happening, the build history for the job shows that it has finished, but the job is still shown in the Build Executor Status and the console log for the build does not show the expected last statement of "Finished: SUCCESS".
This goes on for 5 minutes, which happens to match the configured value of the timeout for calculating the size of the workspace on slaves.
Not sure if this matters, but our jobs are of type: "free-style software project" and the version of Jenkins we use is 1.566
We had version 0.23 of the disk usage plugin, the problem went away by uninstalling the plugin.