In the "Source Code Management" block, if you add an "Additional Behaviours" of "Wipe out repository & force clone", this step fails if the Jenkins user has no permission to delete some objects in the workspace tree.

This situation occurs in my specific situation because dirt left by a prior Docker build is owned by the wrong user. It should instead be deleting the tree using sudo or similar.

A workaround can sometimes be performed, by adding a script step in the previous build to clean out the workspace correctly. This will obviously not work if the previous build fails to get as far as that step.