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
pep8 jobs should not require database setup, etc, so we can skip
running test-setup.sh to save time.
Also, address comments from https://review.opendev.org/670120 and
use a block to not run the stat if can we will skip using the file.
Change-Id: Ia140b331ae1502fcf1f685faa6dace117d77d35d
This allows jobs which inherit from unittests to specify that
the test-setup script should not be run. Some "unit test" jobs
are simple enough that they do not need to perform costly setup
for a full test run.
Change-Id: I5826bed411c42f9b3e0477b351bd82bd964d2fac
The patch will allow jobs to set environment variables and pass
command line arguments to the test-setup.sh script defined by a
project.
This can be used to customize the setup based on the particular job
being run.
Change-Id: I11e1ab15fd2bf3c734544121d9b4040b99ee63da
Did didn't have ansible-lint setup properly, as a results our roles
weren't actually linted properly.
Fix variable linting issues and ignore ANSIBLE0012.
Change-Id: I07aa940245e700c9f08df0f1920720f0ed9d3de0
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We'd like to be able to make some jobs that run tox on other projects
for ease of testing. This should allow us to do that.
Change-Id: I774a76eaaea16d8ea218b439a099b5c9335c2fc5
The original idea was that we'd have a "python27" job. But it turns out
that "python27" isn't actually as universal as you might think.
"tox-py27" on the other hand is a thing that can and should always work
for people who want to run tox with the py27 env.
Port in the jobs we had in openstack-zuul-jobs.
Also, copy in the text of the old shell scripts so that we can iterate on
them and make them better piecemeal.
These are named zuul-tox not tox because we already have tox jobs
defined elsewhere. We'll need to do the naming dance while we work on
them.
Change-Id: I813f3f2ae138c07918556bc81655518023527131
Ian Wienand