Details

    • Similar Issues:

      Description

      The "Full Stage View" view only seems to ever be showing the currently building job any more:

      There was a time when I recall seeing lots of previous jobs, but not any more it seems.

        Attachments

        1. Function.png
          Function.png
          10 kB
        2. image-2019-07-22-13-20-32-346.png
          image-2019-07-22-13-20-32-346.png
          101 kB
        3. Run 592.png
          Run 592.png
          11 kB
        4. Run 593.png
          Run 593.png
          10 kB

          Activity

          Hide
          brianjmurrell Brian J Murrell added a comment -

          Perhaps related, because maybe the stage view is actually only even finding the one single build and not all of them, but the Average stage times: are wrong.  They are always the same as the only stage being shown.

          That tells me that this is not a display problem but a data access problem and that the stage view is showing all of the builds that it can find and it's only finding one.

          But why?

          Show
          brianjmurrell Brian J Murrell added a comment - Perhaps related, because maybe the stage view is actually only even finding the one single build and not all of them, but the Average stage times: are wrong.  They are always the same as the only stage being shown. That tells me that this is not a display problem but a data access problem and that the stage view is showing all of the builds that it can find and it's only finding one. But why?
          Hide
          brianjmurrell Brian J Murrell added a comment -

          This only seems to happen while a job is in progress.  Once the job completes, the older entries show up in the stage view.

          Show
          brianjmurrell Brian J Murrell added a comment - This only seems to happen while a job is in progress.  Once the job completes, the older entries show up in the stage view.
          Hide
          mark_h Mark Hermon added a comment -

          We're seeing the same sort of behavior on our Jenkins. When we did some debugging, it looked like the '#' symbol is causing some confusion when passed back as part of the url to reload the view.

          The team across from us change the build number from '#1234' to their svn revision '1234' and they don't see this problem.

          Show
          mark_h Mark Hermon added a comment - We're seeing the same sort of behavior on our Jenkins. When we did some debugging, it looked like the '#' symbol is causing some confusion when passed back as part of the url to reload the view. The team across from us change the build number from '#1234' to their svn revision '1234' and they don't see this problem.
          Hide
          brianjmurrell Brian J Murrell added a comment -

          This really is quite hideous because this is really the only alternative to Blue Ocean[1] to seeing the individual stages in pipeline jobs.

          Mark Hermon Can you expand a bit on your findings?

          [1]Blue Ocean is too big, bloated and network heavy with it's constant refreshes to be effectively usable.

          Show
          brianjmurrell Brian J Murrell added a comment - This really is quite hideous because this is really the only alternative to Blue Ocean [1] to seeing the individual stages in pipeline jobs. Mark Hermon Can you expand a bit on your findings? [1] Blue Ocean is too big, bloated and network heavy with it's constant refreshes to be effectively usable.
          Hide
          mark_h Mark Hermon added a comment -

          Brian J Murrell I did some more digging, I was mistaken in saying that it was the #. It looks like parallel stages return out of order when they're in progress. I dug through the returned JSON data and found:

          The current run (593):

          The previous run (592):

          It looks like it gets into this function and then bails out because the Stages aren't in the same order.

          I haven't been able to dig any further to see why the stages are returning out of order yet. I could be going in completely the wrong direction.

          Show
          mark_h Mark Hermon added a comment - Brian J Murrell I did some more digging, I was mistaken in saying that it was the #. It looks like parallel stages return out of order when they're in progress. I dug through the returned JSON data and found: The current run (593): The previous run (592): It looks like it gets into this function and then bails out because the Stages aren't in the same order. I haven't been able to dig any further to see why the stages are returning out of order yet. I could be going in completely the wrong direction.
          Hide
          wcoenen Wim Coenen added a comment -

          I have this problem only while parallel stages are executing.

          When the pipeline advances to the next stage without parallelism, I suddenly see past builds again. When the pipeline then advances to a stage containing parallel stages, the past builds disappear again, etc.

          Show
          wcoenen Wim Coenen added a comment - I have this problem only while parallel stages are executing. When the pipeline advances to the next stage without parallelism, I suddenly see past builds again. When the pipeline then advances to a stage containing parallel stages, the past builds disappear again, etc.
          Hide
          gl1koz3 Edgars Batna added a comment -

          The stage view should be redone, as it's too flaky and keeps breaking on simple things.

          I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it.

          Show
          gl1koz3 Edgars Batna added a comment - The stage view should be redone, as it's too flaky and keeps breaking on simple things. I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it.
          Hide
          brianjmurrell Brian J Murrell added a comment -

          I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it.

          Blue Ocean is simply not a suitable replacement for Stage View. It has it's own bugs and issues. It's heavy – it can take many (very many in some cases) seconds to load, it's often "out of date" telling me that it's waiting for a stage to start when the stage is well under way having executed many steps already. Those are just the issues off the top of my head.

          Show
          brianjmurrell Brian J Murrell added a comment - I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it. Blue Ocean is simply not a suitable replacement for Stage View. It has it's own bugs and issues. It's heavy – it can take many (very many in some cases) seconds to load, it's often "out of date" telling me that it's waiting for a stage to start when the stage is well under way having executed many steps already. Those are just the issues off the top of my head.

            People

            • Assignee:
              svanoort Sam Van Oort
              Reporter:
              brianjmurrell Brian J Murrell
            • Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: