In Part 1, I covered the Headless Executionpattern, in which you use public and private keys so that you don't need to log in manually to each machine.
The job submission process can be customized by specifying job activation or expiration time, recurring executionpattern, notification via E-mail upon job completion, and so on.
In the typical execution of the parallel development pattern for practitioners, the owner of a practitioner development stream performs all of these operations.