Testing is a heavy weight process. If you want to scale your services, then you will need to plan to offset most of the work to other nodes.
One evolutionary path for Jenkins in an organization is to start off with one Jenkins master. As the number of Jobs increases, we need to push off the heavier Jobs, such as testing, to slaves. This leaves the master the lighter and more specialized work of aggregating the results.
This recipe uses the Multi slave config plugin (https://wiki.jenkins-ci.org/display/JENKINS/Multi+slave+config+plugin) to install an extra Jenkins node locally. It is Ubuntu-specific, allowing Jenkins to install, configure, and command the slave through SSH.
In Jenkins, install the multi ...