-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major
-
Component/s: junit-plugin
-
Environment:RHEL 7.9
Jenkins 2.334 running in a Docker
Relevant (?) plugins:
jQuery plugin Version1.12.4-1
JQuery3 API Plugin Version3.6.0-2
JUnit Attachments Plugin Version1.7 (current disabled, but no difference when active)
JUnit Plugin Version1.55
Log Parser Plugin Version2.2
Multijob plugin Version1.36
qTest Plugin Version1.4.8
Test Results Aggregator Plugin Version1.2.6
Test Results Analyzer Plugin Version0.3.5
xUnit plugin Version3.0.5RHEL 7.9 Jenkins 2.334 running in a Docker Relevant (?) plugins: jQuery plugin Version1.12.4-1 JQuery3 API Plugin Version3.6.0-2 JUnit Attachments Plugin Version1.7 (current disabled, but no difference when active) JUnit Plugin Version1.55 Log Parser Plugin Version2.2 Multijob plugin Version1.36 qTest Plugin Version1.4.8 Test Results Aggregator Plugin Version1.2.6 Test Results Analyzer Plugin Version0.3.5 xUnit plugin Version3.0.5
Background:Â Previous to the 1.55 release, the JUnit plug-in would faithfully pull our Eggplant test results from their respective Results directories.Â
Expected result:Â Pull the last test result for Jenkins test graphs and for forwarding to qTest.
Actual result: Last week, it started pulling all of the result files; presenting them as new test results from the last run. Each day, it compounds the results with explosive test case "growth"
Troubleshooting/workarounds:Â Â
- qTest plug-in parser works as expected (only recent results)
- Removing old test results from the search path does work, but would destroy our results structure preferred by our Eggplant tool.
- With access to more of the query, we could set a "no earlier than start job time" constraint (just an idea)
Impact
- Test result email broken, since presently it relies on JUnit retrieval for recent test results
