-
Task
-
Resolution: Fixed
-
Minor
-
-
2.259
For Evergreen, we want to detect if already too many logs were generated before the Evergreen Jenkins Plugin even had time to start up.
The rationale being: if there are already 256 logs when plugin startup state is attained, then there is something (very) wrong per-se.
The goal is to be able to do something like:
if (Jenkins.logRecords.size() >= WebAppMain.getDefaultRingBufferSize()) { LOGGER.log(Level.SEVERE, "The Jenkins logs buffer is already full. " + "Some logs might have been missed, and so many logs shows something probably very wrong! (max={0})", maxNumberOfLogs); }
Currently, as an intermediate shim, I'm using reflection. In addition to being dirty, this is likely to become even more an issue to support Java 9 when using such hacks is being made harder and harder.
- relates to
-
JENKINS-49805 Prototype error telemetry logging with a Java Util Logger configuration
-
- Closed
-
- links to
[JENKINS-50669] Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value
Link |
New:
This issue relates to |
Sprint | Original: Essentials - Milestone 1 [ 511 ] | New: Essentials - Milestone 2 [ 516 ] |
Labels | Original: essentials essentials-triggered | New: essentials essentials-triggered technical-debt |
Labels | Original: essentials essentials-triggered technical-debt | New: essentials essentials-triggered evergreen technical-debt |
Labels | Original: essentials essentials-triggered evergreen technical-debt | New: essentials essentials-triggered evergreen evergreen-triggered technical-debt |
Labels | Original: essentials essentials-triggered evergreen evergreen-triggered technical-debt | New: evergreen evergreen-triggered technical-debt |
Description |
Original:
For Essentials, we want to detect if already too many logs were generated before the _Essentials Jenkins Plugin_ even had time to start up. The rationale being: if there are already 256 logs when plugin startup state is attained, then there is something (very) wrong per-se. The goal is to be able to do something like: {code:java} if (Jenkins.logRecords.size() >= WebAppMain.getDefaultRingBufferSize()) { LOGGER.log(Level.SEVERE, "The Jenkins logs buffer is already full. " + "Some logs might have been missed, and so many logs shows something probably very wrong! (max={0})", maxNumberOfLogs); } {code} Currently, as an intermediate shim, I'm using reflection. In addition to being dirty, this is likely to become even more an issue to support Java 9 when using such hacks is being made harder and harder. |
New:
For Evergreen, we want to detect if already too many logs were generated before the _Evergreen Jenkins Plugin_ even had time to start up. The rationale being: if there are already 256 logs when plugin startup state is attained, then there is something (very) wrong per-se. The goal is to be able to do something like: {code:java} if (Jenkins.logRecords.size() >= WebAppMain.getDefaultRingBufferSize()) { LOGGER.log(Level.SEVERE, "The Jenkins logs buffer is already full. " + "Some logs might have been missed, and so many logs shows something probably very wrong! (max={0})", maxNumberOfLogs); } {code} Currently, as an intermediate shim, I'm using reflection. In addition to being dirty, this is likely to become even more an issue to support Java 9 when using such hacks is being made harder and harder. |
Labels | Original: evergreen evergreen-triggered technical-debt | New: evergreen evergreen-triggered n technical-debt |
Labels | Original: evergreen evergreen-triggered n technical-debt | New: evergreen evergreen-triggered newbie-friendly technical-debt |
Sprint | Original: Evergreen - Milestone 2 [ 516 ] |