|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
I use this plugin for all my deployments, and it works great.
I have one feature request that is related to this issue. It would be nice if I could configure 2 different paths... (1) The path the building node actually copies to, and (2) the path that the build page URL references.
Why do I want this?
My Jenkins master is on a Windows Server node. Many jobs build on a Mac slave node. The common location for our deployed artifacts is on a network share that we commonly access in Windows environments via \\server\share notation. On the mac, however, we simply mount the directory and deploy to /Volumes/share. Basically, each node has an env variable that uses the appropriate directory string for its environment so that all builds deploy to ${DEPLOY_PATH}/builds/${BUILD_NUMBER}/so-on-so-forth.
With this strategy, the execution of the builds work great ... in BOTH environments. The issue is the URL to the deployed artifacts on the build page. When it was built on the windows machine, the URLs look like "\\server\share" and users can click them with success. When the mac did the build, the URL says "/Volumes/share/..." and they do not work.
Could the plugin be modified in such a way to allow a workaround to this issue?