Issue: When a pipeline job is already running and another is started the second job will try to execute on an existing build slave. This slave is deleted by job #1 after it completes, at which time job #2 will start a new slave to run in.

Desired: The second job in this instance should not wait for an existing slave container, it should create another one given it's under the pod limit.