-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.424.3
I've repeatedly seen that builds which are aborted during shutdown (sometimes we've to restart Jenkins because of heap problems) are marked as successful when Jenkins starts up afterwards, while they IMO should be marked as aborted.
This is causing problems for us because warning trends reported by the Analysis plugins become invalid at that point.