-
Bug
-
Resolution: Unresolved
-
Minor
-
None
It looks like the "Clone Workspace SCM" plugin is using the display name of the Jenkins job that produces a workspace clone to attempt to locate the workspace that was cloned. This is fine if a display name has not been specified in the "Advanced Project Options" of the job that produces the clone to be restored, but if a display name has been specified then the job configured to use the cloned work space attempts to retrieve the clone from a non-existent directory named for the display name of the job that produced the clone.