We have a heterogeneous Windows/Unix build infrastructure. We'd like to archive build results and have users download from the Jenkins master, but we want the artifacts to actually be archived on a NAS.
If we use a unix-style path as the remote file location, this gets translated to e.g. d:\path\to\archive\file.zip and the download link doesn't work. UNC paths don't work either.
Allowing separate push-to and publish-from locations in the configuration would fix this for us. We could use a UNC path to a Samba share for the Windows build node and the corresponding NFS path for Jenkins to link against on the webpage.