Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-1869

Graphs should not show data points for time periods with no successful builds

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Medium
    • 2.0.1
    • 1.2.4
    • Telemetry / Reporting
    • None

    Description

      From https://support.atlassian.com/browse/BSP-359 :

      Although Bamboo 1.2 and later does collect Clover results for failed builds, it doesn't include their statistics in the Clover graphs. We believe this is what most of our customers would want, because coverage data for failed builds can't be compared against coverage data for successful builds. If we were to include statistics for failed builds, the graph would leap about, and would no longer depict the trend of successful build coverage over time, which is what we believe most of our customers are interested in monitoring.

      The problem is not restricted to Clover graphs.

      For periods of time when you have no successful builds, the graphs show zero values. This too prevents Bamboo users from monitoring the trend over time.

      The problem isn't related to failed builds, as such, it's related to time periods with no successful builds; if you don't run any builds for a period of time, you will see the same problem.

      We're thinking that the best solution may be to modify the graphs so that there is no data point for time periods with no successful builds. There would simply be a straight line segment from the previous time period with a successful build to the next period with a successful build. This would prevent days without successful builds from interfering with the display of the trend over time.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              asridhar AjayA
              Votes:
              7 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: