CPU Saturation During Test Result Merging
criticalResource ContentionUpdated Nov 5, 2024
Jenkins CPU spikes to 100% when merging large volumes of JUnit test results, causing build queue delays and UI slowdowns. This is particularly pronounced when verbose test logging is enabled.
Sources
troubleshooting | bookimarslo.gitbook.io
DevOps Real-Time Troubleshooting: Resolving Common Jenkins Issuesmedium.com
Troubleshooting Jenkins: Resolving Common Issueswww.linkedin.com
Troubleshooting Jenkins Performance: Kubernetes Edition - Part 2www.cloudbees.com
Optimizing Jenkins to ensure fast build times with Dynatracewww.dynatrace.com
How to detect:
Monitor CPU usage on the Jenkins master process. Alert when CPU exceeds 85% for more than 3 minutes, especially during test result aggregation phases. Check for correlation with JUnit TestResultAction.mergeResult execution.
Recommended action:
Reduce test result verbosity and output size. Implement build result retention policies. Consider splitting large test suites into parallel jobs. Monitor JUnit plugin configuration for excessive logging.