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

Some real-time favorite card statuses are not accurate

    XMLWordPrintable

Details

    • 1.0-pre-beta-1, 1.0-beta-1, pacific, atlantic, 1.0-b05/b-06

    Description

      There are some edge cases related to real-time card updates for the Favorites Dashboard which require some SSE changes to adequately address:

      1. Pipeline and Multibranch Pipeline jobs will dispatch "job_started" events as soon as they are run, even if all executors are currently busy. This results in the favorite going into RUNNING status when the user would expect the job is really QUEUED. Tracked by JENKINS-37340
      2. Due to the above behavior, repeated runs of the same pipeline or MB pipeline lead to misleading behavior in the UI. The card will initially reflect the RUNNING state, but after the first job completes it will enter the SUCCESS or FAILED state and remain as such while other jobs are running. This is because no further events are received as the subsequent job runs are actually started.

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. JENKINS-37763 Ad number of "queued" and "running" jobs as properties to Pipeline object

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Task - A task that needs to be done. JENKINS-38540 Add REST API redirects for /runs and /queue

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            kzantow Keith Zantow added a comment -

            cliffmeyers when you have time, please check PR 543 to see if it fixes this issue for you

            kzantow Keith Zantow added a comment - cliffmeyers when you have time, please check PR 543 to see if it fixes this issue for you
            jamesdumay James Dumay added a comment -

            cliffmeyers is this one still a problem or should we close? I haven't heard any complaints.

            jamesdumay James Dumay added a comment - cliffmeyers is this one still a problem or should we close? I haven't heard any complaints.
            cliffmeyers Cliff Meyers added a comment -

            This is still a valid bug, although might be a bit of an edge case. Repro steps:

            1. Favorite a job and leave dashboard open
            2. Open the job in classic
            3. Run it, wait a few seconds, and run again
            4. Abort the first run

            Expected behavior:

            • Job shows as "running"

            Actual behavior:

            • Job shows as "aborted"
            cliffmeyers Cliff Meyers added a comment - This is still a valid bug, although might be a bit of an edge case. Repro steps: Favorite a job and leave dashboard open Open the job in classic Run it, wait a few seconds, and run again Abort the first run Expected behavior: Job shows as "running" Actual behavior: Job shows as "aborted"
            cliffmeyers Cliff Meyers added a comment -

            It's not a bug just in this narrow scenario of course - any situation where there are concurrent runs of the same job and one is aborted / successful / failure will update the favorite card even though the other run is still in-progress.

            cliffmeyers Cliff Meyers added a comment - It's not a bug just in this narrow scenario of course - any situation where there are concurrent runs of the same job and one is aborted / successful / failure will update the favorite card even though the other run is still in-progress.

            People

              Unassigned Unassigned
              cliffmeyers Cliff Meyers
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: