-
Improvement
-
Resolution: Won't Do
-
Major
-
None
Problem statement
Essentials aims at auto-detecting a misbehaving Jenkins instance, for whatever reason.
Analyzing GC logging is the only way to detect correctly for instance that we may have something eating a lot of memory or so.
Proposal
We should enable GC logging on the Jenkins Essentials JVM, because it is a critical part of the story to reliably detect a misbehaving instance.
Complementarily to JENKINS-49805, we should definitely find a way to detect it and report it to participate to some release quality mark [1].
[1] we probably to need to coin a good term for this I guess