All of these invocations of the bindep role are passing what amount to
the defaults. In zuul-jobs, doing bindep_dir: "{{ zuul_work_dir }}" is
important because it allows in-repo uses of those jobs to override how
they work for things like triggering from one repo but running on
another.
The publication jobs in project-config do not need that level of
flexibility, so just remove params and let defaults take over.
As a follow up, we could also add defaults for zuul_work_dir - and
honestly for bindep_dir - to the base job. That way we can always count
on them being set to a sane default value, and they're still
overrideable in a job.
Change-Id: I5bcda84aefa4726d0a904e8bc9698c21ca07f9a5
Both releasenotes and docs build jobs have updated PTI job content.
As a step to rolling it out, update the direct and infra jobs to use the
new direct sphinx method. Also add -python3 versions of the jobs for the
projects that need python3.
The publish-openstack-sphinx-docs job still uses tox. The next patch
will update it as well.
Change-Id: I2d0222225f4ae6c45d09f9352c256062e2535d63
Depends-On: Idd7caf7d88b56d61872906027b4ce7d743572ded
They were both not fetching the same venv they were building with.
Rather than repeat ourselves, we can update these to share a run
playbook - and can pass tox_envlist from the job rather than needing
playbooks that set that themselves. That also allows fetch-tox-output to
pick it up.
Change-Id: Iefec8c50418dcea00c3adebdc20b71c7f20241bd
Monty Taylor