@Daniel, getWorkspaceFor() accepts only an implementation of TopLevelItem, so this will work in case of a free style project, what about other cases ? I tried Jenkins javadoc for some time but I couldn't get a clue.

All projects generally are top-level items. It won't cover matrix axes and similar cases though, where project types divide their workspaces further.

What you could try is to determine the TopLevelItem ancestor of the current build's project, and get the workspace of that on the current node (e.g. /jenkins/workspace/foo). If that's a prefix of the current actual workspace (/jenkins/workspace/foo/bar/baz), just append the rest (/bar/baz) to the workspace path on master

It seems to me that the design of this feature is broken if you need to know about details like that, and an approximation and/or specifically adding support for job types is the best you can do.

What you could try is to determine the TopLevelItem ancestor of the current build's project, and get the workspace of that on the current node (e.g. /jenkins/workspace/foo). If that's a prefix of the current actual workspace (/jenkins/workspace/foo/bar/baz), just append the rest (/bar/baz) to the workspace path on master

Yes, thats what I end up doing as stated in the comment before your reply above.

Yes, thats what I end up doing as stated in the comment before your reply above.

The approach I describe in that paragraph doesn't require any particular knowledge about matrix axes or matrix projects; it wasn't clear from your comment whether yours does.

Actually, yes. "machine/Lin_Test1/temp_axis/1" and "machine/Lin_Test1/temp_axis/2" parts of the path, from my comment, is generated after checking the prefix

Oh, in that case I just didn't understand what you wrote. So you can interpret my recommendation as agreement to what you wrote.

Its okay, I wrote that way for the others to check the output path generated, I wanted to know if they agree to the paths that I am using now for different types of jobs.

Vivek, the target locations on the master that you described for the Multiconfiguration Project look good to me. I look forward to testing the new release of the plugin!

Code changed in jenkins
User: Vivekanand S V
Path:
src/main/java/com/michelin/cio/hudson/plugins/copytoslave/CopyToSlaveUtils.java
http://jenkins-ci.org/commit/copy-to-slave-plugin/6482c22c3a313c0ba8c83c553b1711a3d40c081e
Log:
[FIXED JENKINS-25346] - Addresses the workspace issue where files copied back to master are not in correct path.

@Dan, you can cancel the bounty, thats not needed to make me work, I was (and still am) busy with my personal life, that gives me no time to look here

I think you deserve the bounty as you made the fix we asked for and given me a lot of assistance. I think you need to claim the bounty through the website and then I will gladly pay it. Thanks!