Dustin C. Hatch
b7381b3fb1
It is important that only one configuration management job run at a time. Currently, this is enforced by having only one agent with the *ansible* label, and that agent has only one executor. This is not an ideal solution, because it requires maintaining a separate machine for this purpose. The *Lockable Resources Plugin* provides an alternate solution to this problem. Using this plugin, jobs can acquire an exclusive lock on a "resource" that prevents other jobs that require the same resource from running. Any job that starts while the lock is held will wait until it is released before executing. This will enforce the same serial execution policy, but does not require a separate, dedicated machine. Jobs will be able to run on any executor with the appropriate label. Using this option, it is now possible to run configuration management jobs on the normal agents, defining the execution environment in a Docker image, so the *cm0.pyrocufflink.blue* agent can be decommissioned.