summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2022-11-10 12:32:07 +0000
committerGerrit Code Review <review@openstack.org>2022-11-10 12:32:07 +0000
commitfe49687f29aa2ce778cf1305b051bf60499e0536 (patch)
treed758718692f9f8badb2c4fe61810d77064feb1ef /releasenotes
parent1e1f5ce3a312613fc79ba9de5305cb7972e2a10f (diff)
parentc355adf44e18fc5d8c8e30dccbada1d9bbcd0c19 (diff)
downloadzuul-fe49687f29aa2ce778cf1305b051bf60499e0536.tar.gz
Merge "Add playbook semaphores"
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/playbook-semaphore-0dc1ee618ef77678.yaml11
1 files changed, 11 insertions, 0 deletions
diff --git a/releasenotes/notes/playbook-semaphore-0dc1ee618ef77678.yaml b/releasenotes/notes/playbook-semaphore-0dc1ee618ef77678.yaml
new file mode 100644
index 000000000..77515f3a0
--- /dev/null
+++ b/releasenotes/notes/playbook-semaphore-0dc1ee618ef77678.yaml
@@ -0,0 +1,11 @@
+---
+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.