-
Task
-
Resolution: Duplicate
-
Critical
-
-
tasman
In Scope
- Update the loading of the artifacts tab so that it fetches its data from the new artifacts endpoint built in
JENKINS-39761(similar to how we load the test tab) - Ensure that the name of the artifact is the "full path"
- Add a download all button to the Artifacts tab (see screenshot of https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/job/master/lastSuccessfulBuild/artifact/)
- If we are showing the maximum number of artifacts then show message below "Showing first 100 artifacts"
- duplicates
-
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
- is blocking
-
-
- Closed
-
- relates to
-
-
- Resolved
-
[JENKINS-39737] Update UI to support new artifacts endpoint
Seems like the stash/archive step in pipeline should be creating a zip when it is asked to archive a directory Vs archiving each individual file in the directory, which is what it seems to be doing. If it did that then I think this problem would just go away for BO.
tfennelly yeah it would (it may be doing that behind the scenes) but I think we have to support existing core behavior for now - which allows you to browse a tree on the web vs download or an explosion of files 
jamesdumay unless I am mistaken this is a critical design fault. I had never looked at how artifacts had worked before but the way it seems to work is not feasible. This needs to be looked at ASAP, perhaps even removed for now until it can be solved.