
We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver [1] for the release team [2][3]. Removing 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 [4]. 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. Also these changes remove a stale `setenv`. [1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: I7f1a14d57bdc15b3cf38bb6af8b76939ffdf7765
release-test
Package for testing OpenStack release tools.
This package contains no real useful code and should not need to be packaged by distributors. Its sole purpose is to test the OpenStack release automation tools.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/release-test
- Source: http://git.openstack.org/cgit/openstack/release-test
Description
Languages
Python
100%