Troubleshoot Jenkins Out-of-Memory Failures
Troubleshoot Jenkins Out-of-Memory Failures
Use this checklist when a Jenkins job that supports AIQ workflows fails with an out-of-memory error.
Recommended guidance
- Separate Jenkins controller, agent, build tool, Java, and test-process memory symptoms.
- Review recent changes in dependency size, test volume, browser count, or artifacts.
- Avoid simply increasing memory without identifying the failing process.
- Capture Jenkins logs, build URL, and related AIQ execution IDs.
Validation workflow
- Identify the exact process reporting out-of-memory.
- Review heap, container, agent, and build-tool settings.
- Run a smaller validation job to isolate scale-related failures.
- Apply the smallest safe configuration or workload change and document the result.
Last updated: September 20, 2026