[JIRA] (JENKINS-38538) Old runs disappearing from stage view?
Title: Message Title Sam Van Oort commented on JENKINS-38538 Re: Old runs disappearing from stage view? > 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38538) Old runs disappearing from stage view?
Title: Message Title Sam Van Oort closed an issue as Not A Defect Jenkins / JENKINS-38538 Old runs disappearing from stage view? Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38538) Old runs disappearing from stage view?
Title: Message Title Sam Van Oort commented on JENKINS-38538 Re: Old runs disappearing from stage view? Hi Cornelius Riemenschneider, 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 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38538) Old runs disappearing from stage view?
Title: Message Title Cornelius Riemenschneider created an issue Jenkins / JENKINS-38538 Old runs disappearing from stage view? Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Sep/27 1:12 PM Priority: Minor Reporter: Cornelius Riemenschneider 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? Add Comment
