c355adf44e
This adds the ability to specify that the Zuul executor should acquire a semaphore before running an individual playbook. This is useful for long running jobs which need exclusive access to a resources for only a small amount of time. Change-Id: I90f5e0f570ef6c4b0986b0143318a78ddc27bbde
12 lines
475 B
YAML
12 lines
475 B
YAML
---
|
|
features:
|
|
- |
|
|
Individual playbooks may now be wrapped by a semaphore. Zuul will
|
|
start the job and proceed up to the point of a playbook which
|
|
requires a semaphore and then wait until it is able to aquire the
|
|
semaphore before proceeding. It releases the semaphore after the
|
|
end of that individual playbook.
|
|
|
|
The same semaphore may be used for both jobs and playbooks, but an
|
|
individual job may not use the same semaphore for both purposes.
|