Skip to content

[JENKINS-4976] New build artifact overview is unsorted #19189

Closed

Description

@jenkins-infra-bot

Most likely introduced in build 1.330 (we upgraded from 1.327 to 1.336)

The tree view for build artifacts is unsorted. Previous list was alphabetical ordered.
The list or artifacts we have, starts with a increasing number to benefit from alphabetic ordering


Originally reported by cbos, imported from: New build artifact overview is unsorted
  • assignee: mindless
  • status: Closed
  • priority: Major
  • component(s): core
  • resolution: Fixed
  • resolved: 2009-12-05T09:44:20+00:00
  • votes: 0
  • watchers: 1
  • imported: 2025-11-24
Raw content of original issue

Most likely introduced in build 1.330 (we upgraded from 1.327 to 1.336)

The tree view for build artifacts is unsorted. Previous list was alphabetical ordered. The list or artifacts we have, starts with a increasing number to benefit from alphabetic ordering

Activity

  1. jenkins-infra-bot commented on Dec 2, 2009

    @jenkins-infra-bot
    Author
    mindless:
    • Original comment link
    • Raw content of original comment:

      Do you see unsorted list in simple list view (<17 artifacts) or only in tree view (17-40 artifacts). I don't see any code here regarding sorting, before or after the tree view was added in 1.330, so I would expect the tree to be in arbitrary order and the list to be in whatever order the directory listing returned, which is not guaranteed to be alphabetical. Can we reclassify this as a request to add sorting for both list and tree displays?

    Do you see unsorted list in simple list view (<17 artifacts) or only in tree view (17-40 artifacts). I don't see any code here regarding sorting, before or after the tree view was added in 1.330, so I would expect the tree to be in arbitrary order and the list to be in whatever order the directory listing returned, which is not guaranteed to be alphabetical.
    Can we reclassify this as a request to add sorting for both list and tree displays?

  2. jenkins-infra-bot commented on Dec 3, 2009

    @jenkins-infra-bot
    Author
    cbos:
    • Original comment link
    • Raw content of original comment:

      We have also a job with only 5 artifacts, that list is also unordered. I did compare it with the list of 40+ (which is the same as the workspace file view). That list is ordered. I agree that it is better to have both sorted.

      Another feature we use is the option to download all artifact in a zip. For the jobs we use this feature we have 40+ artifacts, so that is still working http://hudsonserver:8080/hudson/job/cm-trunk-wip-w/lastSuccessfulBuild/artifact/cm/build/isvp/*zip*/isvp.zip This feature is also provided by the workspace file view and very useful with such a long list. We don't use it (yet) for a smaller list, maybe others did. If not it is not required to add it.

    We have also a job with only 5 artifacts, that list is also unordered.
    I did compare it with the list of 40+ (which is the same as the workspace file view). That list is ordered.
    I agree that it is better to have both sorted.

    Another feature we use is the option to download all artifact in a zip. For the jobs we use this feature we have 40+ artifacts, so that is still working
    http://hudsonserver:8080/hudson/job/cm-trunk-wip-w/lastSuccessfulBuild/artifact/cm/build/isvp/*zip*/isvp.zip
    This feature is also provided by the workspace file view and very useful with such a long list.
    We don't use it (yet) for a smaller list, maybe others did. If not it is not required to add it.

  3. jenkins-infra-bot commented on Dec 4, 2009

    @jenkins-infra-bot
    Author
    mindless:
    • Original comment link
    • Raw content of original comment:

      Ok, I plan to add a simple per-directory sort.. I hope that will be sufficient. (the contents of each directory will be sorted, but when shown as a simple list these may not appear sorted if they come from different subdirs in the artifacts tree).

      Regarding zip download, it is always available.. ie, from a build page you can always tack /artifact on the end of the URL to reach the DirectoryBrowser which has the zip download option.. it's just that there is no visible link to this when there are < 40 artifacts.. might be useful to have such a link (but where? hm).

    Ok, I plan to add a simple per-directory sort.. I hope that will be sufficient. (the contents of each directory will be sorted, but when shown as a simple list these may not appear sorted if they come from different subdirs in the artifacts tree).

    Regarding zip download, it is always available.. ie, from a build page you can always tack /artifact on the end of the URL to reach the DirectoryBrowser which has the zip download option.. it's just that there is no visible link to this when there are < 40 artifacts.. might be useful to have such a link (but where? hm).

  4. jenkins-infra-bot commented on Dec 5, 2009

    @jenkins-infra-bot
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original comment:

      Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/java/hudson/model/Run.java trunk/hudson/main/core/src/main/resources/lib/hudson/artifactList.jelly trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=24413 Log: [FIXED JENKINS-4976] Add per-directory sorting for artifact list and tree display. Also, always show a link to directory browser (as "download as zip" is accessible here) instead of only when there are 40+ artifacts.

    Code changed in hudson
    User: : mindless
    Path:
    trunk/hudson/main/core/src/main/java/hudson/model/Run.java
    trunk/hudson/main/core/src/main/resources/lib/hudson/artifactList.jelly
    trunk/www/changelog.html
    http://fisheye4.cenqua.com/changelog/hudson/?cs=24413
    Log:
    [FIXED JENKINS-4976] Add per-directory sorting for artifact list and tree display.
    Also, always show a link to directory browser (as "download as zip" is accessible here)
    instead of only when there are 40+ artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions