We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver  for the release team . Removed specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements . This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug. /!\/!\/!\ Notice that I voluntarily added the doc directory even if no docs are generated here because zuul will try to pull this requirements from there first and the contained requirements are needed for reno but AFAIK the releasenotes dir is ignored by zuul. c.f  for further details. /!\/!\/!\  http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html  https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: Ib224dfe036543c8ec7fe3074fe4280586d35de97
|1 month ago|
|doc||1 month ago|
|tools||10 months ago|
|www||11 months ago|
|.gitignore||1 year ago|
|.gitreview||1 year ago|
|.zuul.yaml||1 year ago|
|LICENSE||9 years ago|
|README.rst||11 months ago|
|bindep.txt||1 year ago|
|test-requirements.txt||1 month ago|
|tox.ini||1 month ago|
This repository contains the index page for https://developer.openstack.org in the www directory.
This repository is in a frozen state, it will be fully retired once a new home is found for the index page.
To build the documentation locally, you must install Python and Python Tox.
To install Tox for Ubuntu 14.04 or later:
apt-get install python-tox python-dev libxml2-dev libxslt1-dev
To build all the documentation after installing Python and Tox:
tox -e docs
To build an individual document, such as the API Guide:
tox -e api-quick-start
The locally-built output files are found in a
To use the same tests that are used as part of our Jenkins gating jobs, install the Python tox package and run
tox from the top-level directory.
To run individual tests:
tox -e publishdocs- Builds all of the documents in this repository, this is called from CI jobs.
Our community welcomes everyone who is interested in open source cloud computing and encourages you to join the OpenStack Foundation.
The best way to get involved with the community is to talk with others online or at a meetup and offer contributions through our processes, the OpenStack wiki, blogs, or on IRC at
We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.
To contribute to the documents, see OpenStack Documentation Contributor Guide.
File bugs on Launchpad and not through GitHub:
To learn more about the OpenStack project, see OpenStack.