Help! My Jenkins is Down!
summary
Provides concrete steps to recover a broken Jenkins instance: capture a thread dump via /threadDump, kill -3 or jstack to find the stuck build and identify the plugin call or sleep causing it; collect slave logs (including EC2) and bundled support artifacts with the support-core plugin to see slow URL requests, deadlocks and CPU-in-thread samples; use jmap heap histogram (not a full heap dump) to spot memory bloat; log bundles cap slow-request captures at 2MB and the support bundle automation proves effective at reproducing and fixing issues.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:28Who Am I
- 6:55Thread Dump
- 8:25J Stack
- 12:09Please Reply to My Http Request
- 14:02Threat Dump
- 18:36Thread Dumps
- 24:31Remote File System Directory
- 37:07Memory Leaks
- 37:38Heap Dump
- 38:15Heap Histogram
- 40:29Monitoring Plugin
related talks
42mHelp! My Jenkins is Down!
38mOperating Jenkins at Scale
30m30 Jenkins features and plugins you wished you had known about before!
44mImproving Software Quality with Jenkins
33mJenkins 101
50mPerformance: Avoiding Pitfalls, Diagnosing Issues & Scaling for Growth
51mIncrease Jenkins High Availability in the Enterprise
46mWorkflow in Jenkins