-
Bug
-
Resolution: Unresolved
-
Major
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
- duplicates
-
-
- Reopened
-
- relates to
-
-
- Open
-
[JENKINS-52711] JUnit Results Trend graph doesn't show all build results if builds have been deleted
| Component/s | New: xunit-plugin [ 15636 ] | |
| Component/s | Original: testng-plugin [ 15801 ] | |
| Description |
Original:
When some of builds were deleted from BuildHistory, TestNG 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 _Note:_ I use job to run tests only and deleting builds by hand sometimes required to cleanup history from false-failed builds (after incorrect changes in job settings, problems with network/environment during tests etc.) |
New:
*Note:* These are the same repro steps from 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 |
| Description |
Original:
*Note:* These are the same repro steps from 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 |
New:
*Note:* These are the same repro steps from 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 |
| Attachment | New: build29.JPG [ 43486 ] | |
| Attachment | New: build30.JPG [ 43487 ] | |
| Attachment | New: build32.JPG [ 43488 ] | |
| Attachment | New: deletebuild30build31.JPG [ 43489 ] |
| Component/s | New: junit-plugin [ 15499 ] | |
| Component/s | Original: xunit-plugin [ 15636 ] |
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
| Summary | Original: Xunit Results Trend graph doesn't show all build results if builds have been deleted | New: JUnit Results Trend graph doesn't show all build results if builds have been deleted |
I have made a pull request to fix this.
https://github.com/jenkinsci/junit-plugin/pull/123
How can I get it reviewed?
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.