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

Stage view for previous builds should not be removed if stages change

      If the stages for the last build were modified (added/renamed/removed) then all stage view history for the previous builds is removed. I don't like this behavior. It is not convenient, because often I need view logs for a certain stage of a certain previous build (even if such a stage does not exist in the current build anymore).

      If the stages for last build don't correspond to the stages of the previous builds it is not a reason to remove the previous ones. It is still possible to display stages for each build independently. It is not a problem if a certain stage is displayed on different positions in different builds. The bigger problem is if it is not available at all like now.

      My proposal is to keep stages for previous builds even if they are different. That is, the stage view history should be not just a matrix, but an ordered list of ordered lists with different size.

      Vizualisazion?
      Each row can be simply independently rendered (the rows can have different length).
      It is possible also to "merge" it and display blank rectangles for whose builds who don't have a certain stage, but it is probably more complicated.

          [JENKINS-61217] Stage view for previous builds should not be removed if stages change

          Alex Taylor added a comment -

          Reclassified as a new feature because this is behaving as designed and will require a significant amount of work

          Alex Taylor added a comment - Reclassified as a new feature because this is behaving as designed and will require a significant amount of work

          Ankur added a comment -

          I face same issue. Created this issue but closed as duplicate after seeing this one. Stage rows from previous builds should still be shown.

          I noticed that when a new stage is added at the end of existing stages then it works as expected. All previous build stages continue to show with the new stage as blank. The behavior should remain same when new stage is added in middle of existing stages.

          Ankur added a comment - I face same issue. Created this issue but closed as duplicate after seeing this one. Stage rows from previous builds should still be shown. I noticed that when a new stage is added at the end of existing stages then it works as expected. All previous build stages continue to show with the new stage as blank. The behavior should remain same when new stage is added in middle of existing stages.

          Tim Black added a comment - - edited

          I've been wondering for a while why this plugin doesn't seem to show many builds ever, and I just found this issue which explains it - we use scripted pipelines and in several places conditionally create and run stages or groups of stages. We also use: `-Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=16` and I never see more than 3-4 builds in any job's stage view. It sounds like this plugin was not designed to support this level of variability in the stages a pipeline could have, correct?

          If so, does anyone know a good alternative? Blue ocean seems good for visualizing individual builds as stages, steps, etc, but I don't know how to make it shows this level of detail for several builds of the same job in one view. Thanks.   

          Tim Black added a comment - - edited I've been wondering for a while why this plugin doesn't seem to show many builds ever, and I just found this issue which explains it - we use scripted pipelines and in several places conditionally create and run stages or groups of stages. We also use: `-Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=16` and I never see more than 3-4 builds in any job's stage view. It sounds like this plugin was not designed to support this level of variability in the stages a pipeline could have, correct? If so, does anyone know a good alternative? Blue ocean seems good for visualizing individual builds as stages, steps, etc, but I don't know how to make it shows this level of detail for several builds of the same job in one view. Thanks.   

          Alex Taylor added a comment -

          timblaktu as of right now the solution is to use Blue Ocean as it will dynamically change the stages you see to show better what your build is doing. Stage view needs a full overhaul of the current nodejs (I think) template process in order to be flexible enough to show different numbers of stages and parallel stages (I assume we would do both that the same time) but that will require a very large time and effort commitment from anyone who would want to solve this issue.

          Alex Taylor added a comment - timblaktu as of right now the solution is to use Blue Ocean as it will dynamically change the stages you see to show better what your build is doing. Stage view needs a full overhaul of the current nodejs (I think) template process in order to be flexible enough to show different numbers of stages and parallel stages (I assume we would do both that the same time) but that will require a very large time and effort commitment from anyone who would want to solve this issue.

            Unassigned Unassigned
            alexander_samoylov Alexander Samoylov
            Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: