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

Old runs disappearing from stage view?

XMLWordPrintable

      Hi,

      this may not be a bug but a support issue...

      Is there anywhere documented how/when old runs are not displayed anymore?
      Sometimes, not even one former run is displayed, sometimes it's up to 9 or so.
      It would be very nice to be able to compare to previous runs...

      There are two things in our setup which could cause this:

      • Our pipeline jobs are autogenerated via the Jobs DSL, and so regularly, so the jobs DSL usually runs in between builds.
      • We skip certain stages dynamically: If the artifact has been built, the stage is never even entered. We do so to now skew the average execution time for a stage, but could this confuse the stage view plugin?

          [JENKINS-38538] Old runs disappearing from stage view?

          Sam Van Oort added a comment -

          Hi cri,
          If you're dynamically changing the stages used, stage view runs into limits in how it can match up stages between runs. In general, you can add stages to the end but not the beginning, but you're better off to make the execution of stage contents conditional (i.e. include empty stages sometimes) than to make the stage itself conditionally executed. This guarantees a consistent stage model.

          I've added a bit more explanation of this to the Wiki's usage notes section - https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin

          The maximum number of runs displayed at any time is controlled by a system property - https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin#PipelineStageViewPlugin-ConfigurableProperties%3A

          I hope that answers your questions? I'm going to go ahead and close this one out, but will be happy to answer the other questions you might have.
          Thanks,
          Sam

          Sam Van Oort added a comment - Hi cri , If you're dynamically changing the stages used, stage view runs into limits in how it can match up stages between runs. In general, you can add stages to the end but not the beginning, but you're better off to make the execution of stage contents conditional (i.e. include empty stages sometimes) than to make the stage itself conditionally executed. This guarantees a consistent stage model. I've added a bit more explanation of this to the Wiki's usage notes section - https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin The maximum number of runs displayed at any time is controlled by a system property - https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin#PipelineStageViewPlugin-ConfigurableProperties%3A I hope that answers your questions? I'm going to go ahead and close this one out, but will be happy to answer the other questions you might have. Thanks, Sam

          Sam Van Oort added a comment -

          > We do so to now skew the average execution time for a stage, but could this confuse the stage view plugin?

          Shorter answer: yes, this confuses stage view.

          Sam Van Oort added a comment - > We do so to now skew the average execution time for a stage, but could this confuse the stage view plugin? Shorter answer: yes, this confuses stage view.

            svanoort Sam Van Oort
            cri Cornelius Riemenschneider
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: