![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
artifactdeployer |
|
Created:
|
19/Aug/14 10:13 PM
|
|
Description:
|
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.
|
|
Environment:
|
Jenkins master: unix
Jenkins build nodes: mixed Windows/Unix
Artifacts archived on a NAS
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Will Saxon
|
|
|
|
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 and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
