Help! My Jenkins is Down!
summary
When Jenkins is sluggish or returning 500s the first diagnostic is a thread dump (via /threaddump, kill -3 or jstack) to find the named build thread and the offending code location; common culprits are long sleeps, bad regexes or slow HTTP calls. A bundled support-core plugin automatically records slow URL requests, ongoing thread samples, deadlocks, and collects master and slave logs (works with EC2); heap issues use heap histograms (jmap) rather than full heap dumps.
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!
50mPerformance: Avoiding Pitfalls, Diagnosing Issues & Scaling for Growth
44mImproving Software Quality with Jenkins
38mOperating Jenkins at Scale
42mSeven Habits of Highly Effective Jenkins Users
40mThe Butler Did It: Putting Jenkins To Work For You
55mContinuous Integration on Steroids
30m30 Jenkins features and plugins you wished you had known about before!