d4c47855ce
We are moving _emit_playbook_banner from zuul_stream to the executor because the data that is meant to be printed inside the banner is not available until v2_playbook_on_play_start which is triggered on every play. This ensures that the banner is only printed once per playbook, even if the playbook has multiple plays. Additionally, we're also printing a 'footer' banner at the end of each playbook in order to provide an explicit and easily parsable result from the perspective of Ansible. This will make it easier for people and systems to parse the job output to find the result of particular playbooks. For example, in Zuul v2, Elastic-Recheck would rely on the last lines of the console to reliably tell when the job was completed and what was it's status. This new v3 approach allows increased granularity by providing the ability to filter down to specific playbooks or even on a phase basis. Change-Id: I7e34206d7968bf128e140468b9a222ecbce3a8f1 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| client.py | ||
| server.py | ||