16eef4ddd4
It's mildly annoying that, in the wake of tagging a new release, documentation lags behind because we only publish in the promote pipeline from what was built by the last change to merge in the gate. There is an existing job which can build and publish documentation in the release pipeline, but does so into a version-specific path leading to multiple versioned copies of the documentation. For fast-moving projects it's not much of a problem since there will be a new change coming along soon to refresh the default version of the documents and reflect the recent tag in page footers and release notes. In simple projects with only a single branch and infrequent changes, however, there can be long periods of time where the published documentation makes no indication of the existence of the latest release. Address this with a new job which publishes to "latest" instead of the tag name. Note that this requires a copy of the existing secret, in order to update the "tag" variable attached to it. Also worth noting, this job could be run in parallel with the existing opendev-publish-tox-docs job in the release pipeline for the same project in order to get the benefits of both. Change-Id: Ibd4f31b9d06137f9cc52bc1a07e1c37766494e7b
303 B
303 B