Since the PTI switched the supported python versions for the current
cycle from 3.8+3.9 to 3.9+3.10, we want to update the constraints
generation accordingly. Since we don't have a stable platform where we
can run both py3.9 and py3.10 in parallel, generate constraints only for
py3.10 for now.
Change-Id: I4a4d9cb6e292bb693ae424be0928501fed81113f
3.10 will come later when there is an image that supports all three
Change-Id: I663de65a971337fce65a51f0e5a7f959b8da2c03
Signed-off-by: Matthew Thode <mthode@mthode.org>
This script creates a virtualenv to run a requirements script to update
constraints. virtualenv is not globally available anymore. Rather than
trying to call it directly, this now uses tox to set up the virtual
environment.
Change-Id: If00afb50c37b45aefbb45070da4efef3e43e62b2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
With change I15d451f6a832b2e698b28e7351a36ef7aea92abe
generate-constraints needs python 3, setup the venv using python 3.
Change-Id: I3dba35267dc6f344ad27910c7dc18c1a33abf4ba
after requirements branches we will remove py27 and py37
Change-Id: I5fde605634108dd628df546a2318731e1832b6b3
Signed-off-by: Matthew Thode <mthode@mthode.org>
This prevents installing unconstrainted versions of libraries for
python3.7. When it was unmapped there was no constraint for it for
certian libraries (some libraries had diferent versions for each version
of python).
Change-Id: I0a5ecc715142756a9ec37fca559fad691651430c
Follow OpenDev changes:
* Use gerrit.opendev.org instead of gerrit.openstack.org
* Use opendev.org insted of git.openstack.org
* Follow move of openstack-infra/project-config to
openstack/project-config
Change-Id: Ic27ea41407abc0bdec29768e5ee5dca33f8adeda
Currently we're running propose-updates forrequirements-constraints
under python 3.5 (on xenial). We take the results of freezing the
constraints fro 3.5 and emit them as 3.4 constraints also. In the near
term[1] we'd like to use the same technique to generate 3.6 constraints.
With the inclusion of I8784509bc162eb6f2e80261bc2d81dbe63ce7989, and
knowing that we no longer run on trusty node, we can now clone the 3.5
constraints freeze to both 3.4 and 3.6. However given that soon we'll
be moving from xenial to bionic this introduces debt that will need to
be fixed after the August release.
Instead just move propose-updates for requirements-constraints job to
bionic now and start cloning 3.6 to 3.5 and 3.4.
Several jobs use propose-updates as a parent so I've made this change
specifically where we call the propose-updates job specifically for
requirements-constraints
Note: This may feel very familiar if you reviewed
I541b64afaee3bf466ff1a461fd2cb472657c4986, The aim is the same but I
mis-understood what propose-update-constraints was doing and it wasn't
the right job and was reverted in I75280b23e2e60800af45dc2343c82008ec9971a9
[1] See re-design discussion:
http://lists.openstack.org/pipermail/openstack-dev/2018-July/132152.html
Change-Id: I1874d4f20a6d69a881f0d9407e159c35ab21542d
This reverts commit c1de884d33cb4fc252e71c5477b87ac5c9ba653b.
propose-updates-constraints != propose-updates. The later does what I want, the former is used by the release-team after releasing a new library.
#eggonface
Change-Id: I75280b23e2e60800af45dc2343c82008ec9971a9
Currently we're running propose-update-constraints under python 3.5 (on
xenial). We take the results of freezing the constraints fro 3.5 and
emit them as 3.4 constraints also. In the near term[1] we'd like to use
the same technique to generate 3.6 constraints also.
With the inclusion of I8784509bc162eb6f2e80261bc2d81dbe63ce7989, and
knowing that we no longer run on trusty node, we can now clone the 3.5
constraints freeze to both 3.4 and 3.6. However given that soon we'll
be moving from xenial to bionic this introduces debt that will need to
be fixed after the August release.
Instead just move propose-update-constraints job to bionic now and start
cloning 3.6 to 3.5 and 3.4.
[1] See re-design discussion:
http://lists.openstack.org/pipermail/openstack-dev/2018-July/132152.html
Change-Id: I541b64afaee3bf466ff1a461fd2cb472657c4986
We do not automatically propose updates to projects' requirements, so
we don't need this branch of logic any more.
Depends-On: https://review.openstack.org/555402/
Change-Id: I511ead56a6a6efecde25ce6b118256aa0560023a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Move proposal scripts from jenkins/scripts to the proposal directory
so that we can install them only for proposal scripts and do not need
to bake them into nodes.
Change-Id: I356906e4a43597cc913bfa539cac7c2c6dfce117
