The install- roles have been renamed to ensure-*, follow the rename.
Depends-On: https://review.opendev.org/716698/
Change-Id: I2522028e9091efdbe292529474de7cce2cf29039
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
The vast majority of changes to enable running releasenotes without
installating of the package itself are merged. Remove the package
install now. Note that install-if-python is the proper role for this,
the previous setting was a noop.
The remaining few changes can merge at any time, projects had enough
time.
See also
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124815.html
Change-Id: I225d73a2f9321329b34a282e08aea6773622df5b
Depends-On: I6d461a69537d3f7dd44e9b9877f652df656eedd8
We were totally missing a run playbook.
For the post playbook we need to not run prepare-docs-for-afs but
instead just do the AFS stamp. Releasenotes are always built from
master.
Change-Id: I7d796f46aa30605ec722e5b442096b0ffd79bcda