74a974bf4e
Like pre-run and post-run, allow a user to run a list of playbooks for a job. One example would be your job workflow would be to run multiple playbooks over using a site.yaml file with include_playbook commands. A second use case, more related to job design. With multiple playbooks support for job.run, the first playbook would be use deploy your server and the second playbook to validate the server was provisioned properly. Today, this can be done using a single run and post-run playbooks, however if post-run fails, zuul will return POST_FAILURE, not FAILURE. Not a large issue, but could be confusing to users when POST_FAILURE is returned. While it is possible a user could create a single site.yaml playbook, and use multiple include_playbook statements to get this functionality, there are downsides to this approach (mostly with the leaking of variables). Today, operators simply run ansible-playbook multiple times with the specific playbooks they only want. Story: 2002543 Task: 22101 Change-Id: I6268d9944e745cc07407ea7dd040fbfeb79dad4d Related-To: https://review.openstack.org/519596 Signed-off-by: Paul Belanger <pabelanger@redhat.com>
5 lines
98 B
YAML
5 lines
98 B
YAML
---
|
|
features:
|
|
- |
|
|
The :attr:`job.run` attribute now supports a single or list of playbooks.
|