Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39737

Update UI to support new artifacts endpoint

    XMLWordPrintable

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      tasman

      Description

      In Scope

        Attachments

          Issue Links

            Activity

            michaelneale Michael Neale created issue -
            michaelneale Michael Neale made changes -
            Field Original Value New Value
            Description When people archive large numbers of files, blue ocean shows this up as lots of items of json test, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing.


            When people archive large numbers of files, blue ocean shows this up as lots of items of json test, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.


            michaelneale Michael Neale made changes -
            Link This issue relates to JENKINS-39661 [ JENKINS-39661 ]
            michaelneale Michael Neale made changes -
            Epic Link JENKINS-35759 [ 171771 ]
            michaelneale Michael Neale made changes -
            Description When people archive large numbers of files, blue ocean shows this up as lots of items of json test, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.


            When people archive large numbers of files, blue ocean shows this up as lots of json objects, flattened out, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.


            michaelneale Michael Neale made changes -
            Description When people archive large numbers of files, blue ocean shows this up as lots of json objects, flattened out, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.


            When people archive large numbers of files, blue ocean shows this up as lots of json objects, flattened out, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.

            NOTE: it seems that with classic it will list the files but only when it is a small amount.
            tfennelly Tom FENNELLY made changes -
            Link This issue is blocking JENKINS-39625 [ JENKINS-39625 ]
            jamesdumay James Dumay made changes -
            Summary Loading all artifacts as flattened list is not feasible Update UI to support new artifacts endpoint
            jamesdumay James Dumay made changes -
            Issue Type Bug [ 1 ] Task [ 3 ]
            jamesdumay James Dumay made changes -
            Description When people archive large numbers of files, blue ocean shows this up as lots of json objects, flattened out, vs a heirachy that can be browsed.

            For example,

            https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipeline-model-definition-plugin/activities/?start=0&limit=1

            Will return 23000 lines of json, much of which is in the artifacts field (nearly 2000 objects, each with 5 or so items).

            This is as a directory structure has been archived with lots of small files, but blue ocean shows this up as a flat listing. This can not scale and seems to be wrong by design.

            The classic jenkins provides a browsable view of artifacts:

            eg

             !Screen Shot 2016-11-15 at 7.44.41 pm.png|thumbnail!

            This doesn't fetch ANY artifact data until it is asked for (vs blue ocean that gives you a flat list).

            The raw json:

             https://gist.github.com/michaelneale/988cfc3ce44458ec9b094ef5dd97c9b3

            The job:
            https://ci.jenkins.io/job/Plugins/job/pipeline-model-definition-plugin/

            The pretty printed json:
             !Screen Shot 2016-11-15 at 7.46.33 pm.png|thumbnail!

            Blue ocean seems a bit wrong by design here - the artifacts tab can't be a flat listing. It should be loaded on demand, and probably never load the whole set of artifacts at once.

            NOTE: it seems that with classic it will list the files but only when it is a small amount.
            michaelneale Michael Neale made changes -
            Attachment Screen Shot 2016-11-15 at 7.44.41 pm.png [ 34848 ]
            michaelneale Michael Neale made changes -
            Attachment Screen Shot 2016-11-15 at 7.46.33 pm.png [ 34847 ]
            jamesdumay James Dumay made changes -
            Description *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)
            jamesdumay James Dumay made changes -
            Attachment Failing result - Artifacts.png [ 34862 ]
            jamesdumay James Dumay made changes -
            Link This issue is blocked by JENKINS-39761 [ JENKINS-39761 ]
            michaelneale Michael Neale made changes -
            michaelneale Michael Neale made changes -
            Description *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)
            *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/)
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35759 [ 171771 ] JENKINS-37957 [ 174099 ]
            jamesdumay James Dumay made changes -
            Labels adoption
            jamesdumay James Dumay made changes -
            Description *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/)
            *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 1000 artifacts"
            jamesdumay James Dumay made changes -
            Attachment Failing result - Artifacts.png [ 34862 ]
            jamesdumay James Dumay made changes -
            Attachment Failing result - Artifacts.png [ 34864 ]
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ]
            jamesdumay James Dumay made changes -
            Assignee Ivan Meredith [ imeredith ]
            jamesdumay James Dumay made changes -
            Description *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 1000 artifacts"
            *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"
            jamesdumay James Dumay made changes -
            Attachment Failing result - Artifacts.png [ 34864 ]
            jamesdumay James Dumay made changes -
            Attachment Failing result - Artifacts.png [ 34865 ]
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ] tasman [ 136 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint tasman [ 136 ] frank [ 156 ]
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ] tasman [ 136 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Link This issue duplicates JENKINS-39761 [ JENKINS-39761 ]
            jamesdumay James Dumay made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              imeredith Ivan Meredith
              Reporter:
              michaelneale Michael Neale
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: