JenkinsGitHub Actions

SCM Webhook Flooding Overwhelming Master

warning
Resource ContentionUpdated Jun 20, 2024

Excessive Git polling and webhook triggers from SCM systems overwhelm the Jenkins master executor queue, causing UI freezes and build delays even when infrastructure is healthy.

How to detect:

Monitor webhook request rate and SCM polling frequency. Alert when webhook rate exceeds baseline by 3x or when executor queue shows excessive waiting jobs despite available executors. Track Git checkout operation frequency.

Recommended action:

Throttle GitHub/GitLab webhooks at source. Add quiet periods to jobs to batch SCM triggers. Use throttle plugin to limit concurrent SCM operations. Disable unnecessary SCM polling in favor of webhooks. Configure webhook filtering to ignore non-relevant events.