Publish documentation at every release
We normally publish documentation updates in the promote pipeline, using documentation built in the gate. As a result, the published docs tend to lag behind release events until the next post-release change lands. Run a separate docs build and publish it on release, so that release notes and version information included in the documentation reflect the most recent tag prior to the next change merging (which for stable projects like this one, could be a while). Override the tag jobvar to force publication to the branch path rather than using a version-specific tree. Also remove ubuntu-focal node overrides for release builds, as this is now our default anyway. Change-Id: I36409682049946bc3f2c9be7af88ba78f01bd8f0 Depends-On: https://review.opendev.org/838525
This commit is contained in:
parent
5d6a6c58b0
commit
e12f9e4f57
10
.zuul.yaml
10
.zuul.yaml
|
@ -59,8 +59,7 @@
|
|||
- bindep-ubuntu-xenial
|
||||
- bindep-ubuntu-bionic
|
||||
- bindep-ubuntu-focal
|
||||
- build-python-release:
|
||||
nodeset: ubuntu-focal
|
||||
- build-python-release
|
||||
- tox-pep8
|
||||
- tox-py27
|
||||
- tox-py35:
|
||||
|
@ -76,8 +75,7 @@
|
|||
- bindep-ubuntu-xenial
|
||||
- bindep-ubuntu-bionic
|
||||
- bindep-ubuntu-focal
|
||||
- build-python-release:
|
||||
nodeset: ubuntu-focal
|
||||
- build-python-release
|
||||
- tox-pep8
|
||||
- tox-py27
|
||||
- tox-py35:
|
||||
|
@ -89,5 +87,5 @@
|
|||
- opendev-promote-python
|
||||
release:
|
||||
jobs:
|
||||
- opendev-release-python:
|
||||
nodeset: ubuntu-focal
|
||||
- opendev-release-python
|
||||
- opendev-publish-unversioned-tox-docs
|
||||
|
|
Loading…
Reference in New Issue