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.

please in what state is this request?
It's needed to have empty directories.
+1

We need to have empty directories as well, is there at least any work-around?

Straightforward workaround: Zip/Tar the build result up as part of the build. Archive those files.

My build output is 3GB. I really have to zip that to get 1 empty dir? Thanks!

I also strongly support this request. There should be no alteration of the build artifacts at all, unless the user explicitly chooses to enable this "feature".