I have a requirement to run a script on all available slave machines. Primarily this is so they get relevant windows hotfixes and new 3rd party tools before building.

The script I have can be run multiple times without undesirable side effects & is quite light weight, so I'm happy for this to be brute force if necessary.

Can anybody give suggestions as to how to ensure that a slave is 'up-to-date' before it works on a job?

I'm happy with solutions that are driven by a job on the master, or ones which can inject the task (automatically) before normal slave job processing.

continuous-integration hudson jenkins
Edit
Report