6d23d20f2f
This is preparation for a later version of ansbile-lint, which finds missing names on blocks. This seems a reasonable rule, and the Ansible manual says [1] Names for blocks have been available since Ansible 2.3. We recommend using names in all tasks, within blocks or elsewhere, for better visibility into the tasks being executed when you run the playbook. This simply adds a name tag for blocks that are missing it. This should have no operational change, but allows us to update the linter in a follow-on change. [1] https://docs.ansible.com/ansible/latest/user_guide/playbooks_blocks.html Change-Id: I92ed4616775650aced352bc9088a07e919f1a25f |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| README.rst | ||
Perform project test setup tasks.
This role assumes that Zuul has checked out a change for a project at
{{ zuul_work_dir }} and looks for a file named
tools/test-setup.sh. If that file exists and is executable,
it will be run.
This allows projects to specify test-setup steps (such as creating or initializing a database) in a form that can be easily run by both an automated testing system and developers.
Role Variables
Environment variables to pass in to the test-setup script.
String of optional command line options passed to the test-setup script.