Currently, when jenkins archives artifacts using the built in artifact management system it links each file to the build information page verbatim (ie: with the path and file name in the link). This works fine in many cases but it would be nice to categorize related artifacts to make them easier to find via the web UI.

Specifically, the use case I had in mind was with respect to Jenkins Pipeline based jobs. Currently there is no way to separate the artifacts gathered from different stages from one another. If the artifact archiver had an optional parameter that would allow the artifacts to be "grouped" or "categoried" together one could pass the name of the current build stage or some other relevant identifier as a "prefix" to use to more easily identify which artifacts are associated with which stage.

Graphically, I was thinking of having a simple expandable-tree view, similar to what is used when a build has a large number of artifacts, with each "root node" in the tree being one of the named prefixes. Then when you expand one of those root nodes the artifacts that were archived with that particular prefix or category would be shown.

If this new parameter were optional it would preserve backwards compatibility, so the changes should be of minimal impact. Further, given the fact there must already be logic within the artifact archiver already for supporting a heirarchal tree structure on the web UI I'm hoping it would be relatively easy to extend that to support a classifier name as well.