-
Task
-
Resolution: Fixed
-
Minor
-
None
-
-
Evergreen - Milestone 1
Per this discussion on jenkinsci-dev, we should prototype whether we can inject custom logger simply through the java.util.logging support already present in the JVM.
The original thread I posted contains some requirements.
I currently define "error telemetry" to include:
- Uncaught exceptions which cause the Evil Jenkins 500 page
- Logged ERROR messages, with or without exceptions
- Logged WARN messages, with or without exceptions
The big question I have in my mind is: can we inject some custom Java code (perhaps this has to be delivered via a plugin?) for reporting exceptions to the Evergreen services layer.
- relates to
-
JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
-
- Closed
-
-
JENKINS-49811 Prototype Evergreen Error service API
-
- Resolved
-
-
JENKINS-50294 Design (JEP) Essentials Instance Client Health Checking
-
- Resolved
-
-
JENKINS-50669 Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value
-
- Closed
-
- links to
Status update: after some experimentation, I submitted a JEP for review on the dev ML https://groups.google.com/forum/#!msg/jenkinsci-dev/IrNOfrlgEEw/MiR5wDiXAQAJ
The implementation for demonstration of feasibility is filed at https://github.com/jenkins-infra/evergreen/pull/43 on evergreen, using https://github.com/batmat/essentials-plugin on my GH account for now before I have the community agreement it's the right path, and I move it to the jenkinsci org.