-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Minor
-
Component/s: coverage-plugin, maven-plugin
-
Environment:Jenkins 2.504.3 (viewed on 2.504.2 too), with embedded Jetty on Linux RedHat 8.
All plugins up to date. Coverage plugin 2.7.0.
Sometimes, jobs with coverage analysis have their status, coverage values and execution date incorrectly loaded as shown in attached files.
=> job 212 was OK before restart but has problems after it.
This happens randomly, not always on the same jobs when Jenkins restarts.
When it occurs, Jenkins shows a warning on old value in jobs definition which reveals a ConcurrentModificationException. (also in attached files)
