always make the requirements repo available for release jobs
Most of the python jobs for libraries need to check out the
requirements repo as part of setting up their tox environment.
# NOTE(dhellmann): Several projects that depend on neutron or
# horizon for their testing use a special install script run via
# tox that tries to use zuul-cloner to make the dependency
- # available before installing it from source. Until we change
- # the PTI for building sdists and wheels from Python projects so
- # that it does not use tox, we need to ensure those repos are
- # present for zuul-cloner to copy. Both openstack/neutron and
- # openstack/horizon can be removed from the list of
+ # available before installing it from source. All libraries
+ # require openstack/requirements for the custom install scripts
+ # they run via tox. Until we change the PTI for building sdists
+ # and wheels from Python projects so that it does not use tox,
+ # we need to ensure those repos are present for zuul-cloner to
+ # copy. The openstack/neutron, openstack/horizon, and
+ # openstack/requirements repos can be removed from the list of
# required-projects for this job when the job is modified to not
# use tox.
- name: openstack/neutron
- name: openstack/horizon
+ - name: openstack/requirements
secrets:
- secret: pypi_secret
name: pypi_info
- gpg_key
+ vars:
+ # NOTE(dhellmann): Library projects using a custom installation
+ # script need to be told where the constraints file is. We can
+ # remove this when tox is no longer part of the CTI for building
+ # sdists.
+ tox_constraints_file: "{{ ansible_user_dir }}/src/git.openstack.org/openstack/requirements/upper-constraints.txt"
- job:
name: publish-openstack-sphinx-docs
