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

JUnit Results Trend graph doesn't show all build results if builds have been deleted

      Note:
      These are the same repro steps from JENKINS-32746 but for Xunit.

      When some of builds were deleted from BuildHistory, Xunit Results Trend graph does not show all preceding builds anymore.

      Steps to reproduce:
      1. Make several builds (#1, #2, #3) with test results.
      2. Make one more build (#4). Delete it manually from build History
      3. Make few more builds (#5, #6) and see to graph.
      *Expected result: *graph contains build #1, #2, #3, #5, #6 (all but deleted)

      • Actual result: *graph contains only results after deleted one: #5, #6

       

        1. build29.JPG
          build29.JPG
          54 kB
        2. build30.JPG
          build30.JPG
          53 kB
        3. build32.JPG
          build32.JPG
          51 kB
        4. deletebuild30build31.JPG
          deletebuild30build31.JPG
          56 kB

          [JENKINS-52711] JUnit Results Trend graph doesn't show all build results if builds have been deleted

          Nikolas Falco added a comment - - edited

          XUnit use the TestResultAction of junit plugin (1.24) that has the same behavior (tested just now). It suppose there are no gaps between builds and for me have sense (what is the reason to remove manually a build?)

          In TestNG plugin (JENKINS-32746) owner has decide to patch locally. If the owner of JUnit plugin agree with you it is a bug and fix the issue, the fix will available for all plugin that use junit like xunit.

          I'm reassign the issue to junit plugin.

          Nikolas Falco added a comment - - edited XUnit use the TestResultAction of junit plugin (1.24) that has the same behavior (tested just now). It suppose there are no gaps between builds and for me have sense (what is the reason to remove manually a build?) In TestNG plugin ( JENKINS-32746 ) owner has decide to patch locally. If the owner of JUnit plugin agree with you it is a bug and fix the issue, the fix will available for all plugin that use junit like xunit. I'm reassign the issue to junit plugin.

          Greg Hester added a comment -

          Thanks for input.

          Greg Hester added a comment - Thanks for input.

          Ilya Ilba added a comment -

          I have made a pull request to fix this.

          https://github.com/jenkinsci/junit-plugin/pull/123

          How can I get it reviewed?

          Ilya Ilba added a comment - I have made a pull request to fix this. https://github.com/jenkinsci/junit-plugin/pull/123 How can I get it reviewed?

          Jesse Glick added a comment -

          Very likely a duplicate of something much older.

          Jesse Glick added a comment - Very likely a duplicate of something much older.

          Ilya Ilba added a comment -

          There are other manifestations of the same issue in the code, e.g. JENKINS-31926, JENKINS-26153, JENKINS-25340. But this ticket is unique in that it describes specifically deleted builds - which is exactly the issue which I had.

          Ilya Ilba added a comment - There are other manifestations of the same issue in the code, e.g. JENKINS-31926 , JENKINS-26153 , JENKINS-25340 . But this ticket is unique in that it describes specifically deleted builds - which is exactly the issue which I had.

          Any news concerning this issue?

           

          Alexander Schmidt added a comment - Any news concerning this issue?  

            il__ya Ilya Ilba
            greg_hester_avalara Greg Hester
            Votes:
            6 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: