I added previously a check that makes docs job fail in post if there's no
html output. This now leads to a POST_FAILURE when the normal build fails.
So, a FAILURE turned into POST_FAILURE, see
https://zuul.opendev.org/t/zuul/build/afbc8c39929a46039aa4d987971cdb4f .
Update the check in the fetch-sphinx-tarball role that it only fails
if the playbooks passed.
Change-Id: Iebd0bffcc5caaa6df97d432a712d83b64db8e780
Fix bug which prevented find from finding builds when the
folder was a symlink. This can happen if a project using a different
build layout tries to expose the docs at the expected location.
Change-Id: Ib7782b60cef42d2e9fd3077791f06b0f918d7c45
If no html is generated but a PDF, the role will succeed. This is wrong,
we always need HTML for the publish step where the logic is: Publish
HTML and optionally PDF.
I run into this when updating tox.ini and breaking html output, the jobs
passed but promote job failed.
Change-Id: I44d15da4c8e1ec0d1f7284daed69dbf5caa40bf0
This enhances fetch-sphinx-tarball to fetch PDF files as well if
they are published
For now, it collects a single PDF file since sphinx only generates one.
The name of the PDF file is not known in advance.
The publishing is done with https://review.opendev.org/678142.
This will then be used by https://review.opendev.org/664555.
Change-Id: I872ab1f696495dc40cb845e0eee5f6f0ffe892d8
With the arrival of ansible-lint 4, Jinja2 variable expansions must
include spaces before and after the variable name inside the
brackets.
Adjust the new violations accordingly and remove the rule
206 exclusion.
Change-Id: Ib3ff7b0233a5d5cf99772f9c2adc81861cf34ffa
This is a new artifact-aware method of fetching sphinx tarballs,
meant to be used in docs promote jobs.
Change-Id: I9a01af9e36b959c4fa42f3c41b548c87bf2e1759
Tristan Cacqueray