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

Loading worm shows for every update run SSE event

XMLWordPrintable

    • Blue Ocean 1.4 - beta 3

      Problem
      On busy servers the loading worm shows for SSE events that update the run in the store

      Steps to reproduce

      1. Open the dashboard page in a new browser window
      2. Open a Pipeline in another window side by side
      3. Run the Pipeline over and over again
      4. Loading worm will flash on the dashboard page

      What you should see
      Loading worm should only be shown for navigational purposes but never for random SSE event fetches.

          [JENKINS-48306] Loading worm shows for every update run SSE event

          James Dumay added a comment -

          kzantow was shown https://builds.apache.org/blue/organizations/jenkins/pipelines/ and thinks we are fetching this data prematurely. He said that we should only fetch data on SSE when there is a run or pipeline in the cache.

          James Dumay added a comment - kzantow was shown https://builds.apache.org/blue/organizations/jenkins/pipelines/ and thinks we are fetching this data prematurely. He said that we should only fetch data on SSE when there is a run or pipeline in the cache.

          Cliff Meyers added a comment -

          I'm happy to take this one on if you feel it's high priority jamesdumay

          Cliff Meyers added a comment - I'm happy to take this one on if you feel it's high priority jamesdumay

          Cliff Meyers added a comment -

          There is second issue that I noticed on the apache build server URL above. It seems that "downstream Maven projects" are pushing a lot of SSE at the UI, but also the URL's being returned do not properly resolve and result in a 404. I will probably file a separate ticket to cover that, we just need to be careful because if we fix the "wasteful fetches" problem in this ticket it will probably cover up the other bug I'm seeing here.

          Cliff Meyers added a comment - There is second issue that I noticed on the apache build server URL above. It seems that "downstream Maven projects" are pushing a lot of SSE at the UI, but also the URL's being returned do not properly resolve and result in a 404. I will probably file a separate ticket to cover that, we just need to be careful because if we fix the "wasteful fetches" problem in this ticket it will probably cover up the other bug I'm seeing here.

          Karl Shultz added a comment -

          Good coverage is included as part of the PR.

          Karl Shultz added a comment - Good coverage is included as part of the PR .

            cliffmeyers Cliff Meyers
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: