|
||||||||
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
For us, this is more than a "Minor" priority issue - it's causing the application that was written to expect the folder to be there to fail. I don't understand the logic behind why this was set to never allow you to copy empty directories. The build itself always has the ability to remove empty directories if they aren't desired before archiving. However, if you do desire empty directories in the artifacts, then with this change in, it is impossible to implement this. If, for example, we did not have the source code (vendor binary package), and we used Jenkins as our enterprise solution for "packaging", there would be no work-around. There is always a work-around for "deleting" unnecessary directories from a build, though - don't create them - delete in build script - added "batch command" build step - etc. I think this alone is enough to justify at least an option to include empty directories.