|
||||||||
|
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, send email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This is not an issue of ws cleanup plugin, but rather in Jenkins core as it uses Jenkins core functionality or deleting workspaces. It's usually caused by a file, which cannot be deteled (e.g. still open by another process). In such cases Jenkins tries to chmod upper directory (i.e. it's a feature, not a bug![]()
), which sometimes (especially on Unix) results into what you described. Moving into the "core" component.