[ 
https://issues.jenkins-ci.org/browse/JENKINS-12311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161816#comment-161816
 ] 

bogdaniosif edited comment on JENKINS-12311 at 4/20/12 2:20 PM:
----------------------------------------------------------------

Please make this behaviour optional. I can't use this plugin past v0.15 because 
of this change.

My arguments:
- Full paths on the build server are now visible to web ui users, which is 
highly undesirable
- When a user wishes to save an artifact locally, the name generated by the 
browser for the file to be downloaded is unusable as it is actually the full 
path of the file on the build server, meshed together by removing path 
separators

For me, the behavior pre 0.16 was ideal because I'm archiving a couple of 
zipped packages per build which actually have by design unique names and it 
makes perfect sense to have them in a flat view.

Please make this behavior optional. I was very thankful to have found this 
plugin at v0.7 and I find this change terrible. Please see the attached 
screenshots.
                
      was (Author: bogdaniosif):
    Please make this behaviour optional. I can't use this plugin past v0.15 
because of this change.

My arguments:
- Full paths on the build server are now visible to web ui users, which is I 
find undesirable
- When a user wishes to save an artifact locally, the name generated by the 
browser for the file to be downloaded is unusable as it is actually the full 
path of the file on the build server, meshed together by removing path 
separators

For me, the behavior pre 0.16 was ideal because I'm archiving a couple of 
zipped packages per build which actually have by design unique names and it 
makes perfect sense to have them in a flat view.

Please make this behavior optional. I was very thankful to have found this 
plugin at v0.7 and I find this change terrible.

Please see screenshots. They tell a good story of just how unusable things have 
suddenly become.
                  
> Display the Deployed Artifacts in a tree structure similar to how they are 
> displayed under the Build Artifacts section
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12311
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12311
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: artifactdeployer
>    Affects Versions: current
>            Reporter: Chris Williams
>            Assignee: gbois
>            Priority: Minor
>         Attachments: artifact-deployer-plugin.jpg, Post 0.15 behavior.jpg, 
> Pre 0.16 behavior.jpg
>
>
> Currently the deployed artifacts are always presented in a flattened format 
> on the Jenkins job/build page. Additionally, if there are multiple artifacts 
> with the same name, but in different directories, the Deployed Artifacts 
> section will only display one file, with no indication which version of the 
> file it is. (see attached screenshot)
> I'd like to see the Deployed Artifacts displayed in a directory-tree 
> structure (similar to the normal Build Artifacts section). 
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to