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

Queued items are not showing up

    XMLWordPrintable

Details

    • 1.0-m10

    Description

      I ran this job on blueocean.io

      It didn't show up as queued

      Calling the REST API there is nothing in the runs

      charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/runs/ | json_pp
      []
      

      But there seems to be items in the queue

      charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/queue/ | json_pp
      [
         {
            "pipeline" : "freestyle",
            "id" : "545",
            "_class" : "io.jenkins.blueocean.service.embedded.rest.QueueItemImpl",
            "queuedTime" : "2016-06-24T04:53:33.867+0000",
            "_links" : {
               "self" : {
                  "href" : "/blue/rest/organizations/jenkins/pipelines/freestyle/queue/545/",
                  "_class" : "io.jenkins.blueocean.rest.hal.Link"
               }
            },
            "expectedBuildNumber" : 1
         }
      ]
      

      Attachments

        1. blue.png
          blue.png
          265 kB
        2. classic.png
          classic.png
          166 kB

        Issue Links

          Activity

            cliffmeyers Cliff Meyers added a comment -

            I think we can make this work okay with two calls. If down the road we need start adding more calls for additional features, we may need to consider combining runs and queued items into a single call but for now I think we could get away without doing that. tscherler what do you think?

            jamesdumay how should we sort the data on this screen? Would all queued items always display at the top of list, "ahead" of anything that was run or is currently running?

            cliffmeyers Cliff Meyers added a comment - I think we can make this work okay with two calls. If down the road we need start adding more calls for additional features, we may need to consider combining runs and queued items into a single call but for now I think we could get away without doing that. tscherler what do you think? jamesdumay how should we sort the data on this screen? Would all queued items always display at the top of list, "ahead" of anything that was run or is currently running?
            jamesdumay James Dumay added a comment -

            how should we sort the data on this screen? Would all queued items always display at the top of list, "ahead" of anything that was run or is currently running?

            cliffmeyers that works for me. They should be ordered by their queued date?

            jamesdumay James Dumay added a comment - how should we sort the data on this screen? Would all queued items always display at the top of list, "ahead" of anything that was run or is currently running? cliffmeyers that works for me. They should be ordered by their queued date?

            Yeah two calls would work, but preferable we use it in combination with sse, meaning if the queue changes we refetch that change if we still interested in that change. ...but that is basically what vivek is saying with the QueueListener, in which we should then fire sse for ux.

            tscherler Thorsten Scherler added a comment - Yeah two calls would work, but preferable we use it in combination with sse, meaning if the queue changes we refetch that change if we still interested in that change. ...but that is basically what vivek is saying with the QueueListener, in which we should then fire sse for ux.
            cliffmeyers Cliff Meyers added a comment -

            Right but on initial page load we still need to make a call to fetch the queue, otherwise if the user is coming in for the first time and many builds are queued, they won't display. We just need to test whether the REST API is currently fetching enough data for a queued item to reasonably display. In all my local testing, anything that gets queued immediately goes into run state. Guess I should decrease the number of executors next time I test.

            cliffmeyers Cliff Meyers added a comment - Right but on initial page load we still need to make a call to fetch the queue, otherwise if the user is coming in for the first time and many builds are queued, they won't display. We just need to test whether the REST API is currently fetching enough data for a queued item to reasonably display. In all my local testing, anything that gets queued immediately goes into run state. Guess I should decrease the number of executors next time I test.
            vivek Vivek Pandey added a comment - PR https://github.com/jenkinsci/blueocean-plugin/pull/305 submitted.

            People

              vivek Vivek Pandey
              jamesdumay James Dumay
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: