Summary
The build starts to run gmake at some point instead of using Electric Make (eMake). This causes one big job on that cluster host, instead of parallel jobs.
Solution
This is most likely caused by the Makefile or a script file invoking gmake or nmake directly (not using $(MAKE) or eMake as the application to invoke. You can either switch to using the MAKE macro, or rename eMake to gmake/nmake and put that executable before the original gmake/nmake.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.