At the moment, the tox_envlist is defined inside the include_role
for tox as releasenotes. This means that other roles which run
beforehand such as tox-siblings will use the default value of
venv instead which isn't always defined.
This patch makes the change to make that variable defined in
the job which means that all other roles will reference the correct
tox envlist in the entire job run.
Change-Id: I0323f8f1bccf720268d947b8e1dcb6c5f8b26dfa
The parent of the build-openstack-releasenotes job is openstack-tox
which means that there is no point in defining tox_constraints_file
as it is already globally defined in openstack-tox.
Change-Id: I5f7d58dcd4c300e6b700a972c05e43c5d146765a
reno expects to be run on the master branch, so add an 'override-branch'
setting to the job.
While we're in there, add a description and remove the tox_envlist var,
as it is hard-coded inside of the role.
Change-Id: Ide918d1bb631590683f96bddc6b43c12c7ab5ac2
Originally, we were moving the release notes to another folder
to make it work with the fetch-sphinx-output role. However,
this did not always work as expected due to the fact that some
projects do not have a doc folder.
This fixes that issue and avoids the move and simply grabs the
data from the right folder.
Change-Id: If6ee519c33320db91f8a9553ed4abc099c284eec
The past bash code had two paths for building release notes, it
makes it much harder to refactor and debug (for example, the result
was being moved only if the release notes had translations).
Change-Id: I45272750fc734566d08329d915fbedc10b9eed65
