A Webhook Storm Made Branch Scans Eat Every Executor — Jenkins Multibranch Pipeline
на канале: TheCodeForge
A Multibranch Pipeline scan triggered by a webhook on every push across 200+ branches — the scans themselves consumed executors until all 8 were exhausted. This is Multibranch Pipelines explained: automatic branch discovery, the Jenkinsfile-per-branch model, PR builds, and tuning scan triggers so indexing doesn't starve your builds.
⏳ Timestamps:
0:00 - Cold open: 8 executors exhausted by 200+ branch scans
0:19 - Intro
0:26 - What Is Multibranch Pipeline?
0:45 - Why Multibranch Pipeline Exists
1:07 - Basic Jenkinsfile Structure
1:38 - Setting Up Multibranch Pipeline
2:17 - Branch-Specific Logic
2:51 - Handling Pull Requests
3:28 - When Multibranch Breaks
4:06 - 8 executors exhausted by 200+ branch scans
4:27 - Incident Deep-Dive: The Fix
4:45 - ⚠ Gotcha: Webhook-only scan without throttle
4:56 - ⚠ Gotcha: Relying solely on webhooks for large repos
5:06 - ⚠ Gotcha: Running Jenkinsfile from untrusted PR source
5:19 - ⚠ Gotcha: Not configuring orphaned item strategy
5:37 - Version Compatibility: Branch API Plugin
6:13 - Production Caveat: Scan Timeout
6:32 - Debugging Guide
6:49 - Interview Questions
7:12 - FAQ
7:33 - Key Takeaways
7:52 - Next up
8:04 - Wrap-up
👉 Full article + code: https://thecodeforge.io/devops/jenkin...
⏭ Next up: Jenkins GitHub Integration and Webhooks
#jenkins #devops #cicd