Switch our docs job to use opendev-tox-docs job as base so that we can
publish later the content from gate directly (via promote queue) and do
not need to rebuild in post again.
Use the new promote-openstack-manuals job as first step in using promote
publishing. The other publish jobs will be replaced separately.
Use for building now publishdocs/publishlang so that we have exactly
the same content in check and gate - and in the published website.
For this, update tox.ini and publish script.
Also, do not publish project-data.
Depends-On: https://review.opendev.org/676489
Change-Id: I91f22173a4a6ed421f339833c486a31fd319dba3
Publishing to a top-level directory has a few challenges with some new
infra scripts. Let's keep those simple and change from publish-docs to
publish-docs/html.
Depends-On: https://review.opendev.org/676489
Change-Id: I94b7bf915c0fdad0e9e2f5dd81846f45dc99194a
These parameters will produce the same output directory path, but
will enable the role to return the correct preview artifact url.
Depends-On: https://review.opendev.org/676437
Change-Id: I65a5c6616eb5725f175df7d67cbf05bca9ba03a3
Add native zuul v3 templates and job for building doc projects. The
templates can be used by api-site and security-doc as well.
Create extra templates for publishing to developer.openstack.org.
Leave in a TODO for publishing, these post jobs will be added when
ready.
Change-Id: I377632e640a099d0a8640db4959684d9ecd68f8c