Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
Jenkins Version 2.249.3
Description
When upgrading to version 1.44 of the Junit plugin, I start getting the following Jenkins errors for most of my pipelines:
Downgrading to version 1.43 of the plugin resolves the issue.
If it matters, I'm using Nunit to run our tests and using the attached xslt to convert to the Junit format. I don't think that's the issue, since it is giving the MissingFieldException for pipelines that don't run any tests as well.
Attachments
Activity
Chris Page
added a comment - The list grows with each pipeline that runs. Even after discarding, it comes back. In the text above, it says that it impacts Jenkins startup time, and it shows as an alert for users with the permissions to see alerts. Whatever is checking for that field needs to fail gracefully such that it does not raise these kind of errors.
Chris Page
added a comment - The list grows with each pipeline that runs. Even after discarding, it comes back. In the text above, it says that it impacts Jenkins startup time, and it shows as an alert for users with the permissions to see alerts. Whatever is checking for that field needs to fail gracefully such that it does not raise these kind of errors. Same issue here after upgrading form junit:1.43 to junit:1.46 and core 2.263.1
you can discard the unreadable data, it shouldn't cause any issues