We now have a stable/pike branch and mitaka is EOLd (though we can't yet
remove the branch because there are still projects that are using it :(
Update the grep-all script to look in releases we care about.
Change-Id: Ia3eeda9db6b5715a3bfff5fe4f0ccd3d50ebf653
When I added the license to grep-all I copied it from another shell file
clearly no one read it as it describes tools/cruft.sh
Change-Id: Ia48d5000a360519be596c09273ba653d10e3daa6
If you run grep-all.sh requests, you get all the item that match that
prefix. It is a little messy. Make the match patten more specific so
you only get the library you pass on the command line.
Change-Id: I16544372f7efff28933da728d11f85dc5e5f9aea
Often it's helpful to quickly compare the requirements and constraints
for a given library on all branches. This tool does that.
Change-Id: I2458c5929d8812cd74f657050eea5f4f3fa11df0
We need the integration gate to work with both trusty (python3.4) and
xenial (python3.5). Rather than hard code the full python binary just
use python 3 and let the OS mange this for us. This is less than ideal
but it's the best we can do right now to unblock the gate.
We also address a short term issue with out upper-constraints.txt files
and manually copy the constraints from 3.4 to 3.5
Related-Bug: 1620436
Change-Id: I6acabf86933b7a7bce7baf44e6b512e7d0d2f6db
This change creates a new tox environment that *only* installs
openstack_requirements and then verifies that each of the console
scripts has all of the modules that it imports.
This will need to be added to our gate RSN
Change-Id: Ibc37593afcc4d9f820cb88168e1aa15e773b2087
If we don't do this then the following line:
weakrefmethod;python_version=='2.7' or python_version=='2.6' # PSF
ends up as:
weakrefmethod;python_version
in the cruft output. So we need to add ';' to get the output
as 'weakrefmethod'
Change-Id: I7b32bfe70df3bb24ca301db9952d76451674a0db
With Babel 2.2 and then with Babel 2.3.2 and 2.3.3 releases, the
OpenStack infra scripts broke and uncovered bugs in the upstream
Babel release. The infra scripts run in post and periodic queues, so
failures here are not directly visible. With Babel 2.3.x invalid strings
were send to the translation server, and we had to recover old content
to fix this.
Let's add some Babel integration tests that can be run whenever the
upper-constraints file changes so that any new Babel release will be at
least minimally tested.
The shell script babel-test.sh runs a simple extraction of strings to
translate from a simple input file. It uses the same commands that the
infra scripts run and handles the two different cases of extraction of
the normal strings and extraction of the non-standard log-level strings.
The script then compares the new content with previously created good
content.
Once this change is in, we will run this test whenever
upper-constraints.txt file changes.
Needed-By: I15fa6a706323615d6072d8acaa859fea9bf35883
Change-Id: Iab7844ba748ecd84ec07ad4280b2317bd626fe9a
We need to test without committing the requirements changes because pbr
throws an error if the pre and post versioning do not match. The first
change on a stable branch must be the one to remove the pre-versioning
configuration.
Change-Id: I812af614b7a6c7f499c67310f078ac4835b9e91a
We have removed these projects from the PROJECTS list so no longer need
to special case them here.
Change-Id: Ic3116a646389438ded03f285819529477bf849d8
Depends-On: I61c2f3f8a724dc789479278e7ba493e095c52305
bindep makes this a lot easier to work with as well as making it
possible to support Fedora, Suse etc as needed.
Change-Id: I4d19df8bbcd08e06edcf71ee51c30bb9c3d57fd0
This reverts commit ce6ef0fe230ff939ae4d583a2262a16d598c32b9
We're only installing bindep on diskimage-builder built images, and
the devstack-trusty images in rax regions are snapshot-based. We'll
need to temporarily revert this until devstack-trusty is switched to
DIB everywhere, or DevStack-based jobs move to the ubuntu-trusty DIB
images we have available in rax currently.
Change-Id: I69c923297c3202fd35b8892ddfa4d8dbf272bf16
Closes-Bug: #1475880
bindep makes this a lot easier to work with as well as making it
possible to support Fedora, Suse etc as needed.
Change-Id: I29ffd7376c6f77ca104bf7d930fef178e5cab20f
This required some care. There doesn't seem to be a sane Python3 ready
comment-preserving ini parser around, so I wrote a
minimal-for-our-case one in Parsley. Parsley is already in use in
infra in bindep, but I need to add it to global-requirements as this
is the first use in a managed project of it.
Change-Id: I48de3a2f36e945f75b534f689e3af802bbdc5be9
Depends-On: I7d7e91694c9145fac0ddab8a9de5f789d723c641
Depends-On: I16e967356d5c56f1474ee661b954b3db11a608cb
Pyngus 1.3.1 has been released and it fixes the issues that blocked the
gate last time. This version of the library is required for the amqp
driver in oslo.messaging.
Change-Id: I4ba583e062674b27ad873ca2228274f383f2bb22
We want to use the new resolver branch of pip today, and perhaps
develop in future too. This introduces the same basic change we did to
pbr's tests to test with a custom pip.
Change-Id: Ia2b1a9c7ee7a7bf32f404932fe7fe872ac402b0e
Depends-On: I7600fa20391bb83491d630b277bf01cc3a20727c
It broke us today, it will probably do so in the future. Let's track
it.
Depends-On: If48a8444b02ee1e105bc1d9ce78a0489ea0c405b
Change-Id: I203738fad804d3cd41808109a1671e4baabf48d0
This runs through all of global-requirements.txt and looks at the
release history of all components over the last N days, returning the
released list. This is helpful in unexplained gate breaks to at least
look for candidate libraries.
Fleshed out some docs to explain intent for future consumers /
modifiers of this script.
Change-Id: I5880a1d7f0a6063a45f7533319fed1ff56057144
We've hit a situation where a project (pycadf) is listed and capped
in stable/icehouse requirements.txt. pycadf is also listed in
projects.txt. As part of the requirements integration test, we are
attempting to update pycadf's master branch with stable/icehouse
requirements, and failing because of new dependencies in pycadf that
are not managed by stable/icehouse's GR.
This updates integration.sh so that when we're testing a stable branch,
we are only syncing requirements to other projects have stable branches.
This avoids trying to sync stable requirements into library's master
branches.
Change-Id: I3b8845ad8e013cf6747995df5a62cc4f2ee85e01
It seems that there is a bug in (old?) versions of git, particularily in
the one that is shipped with Ubuntu Precise (1.7.9.5) that (sometimes?)
makes the exit code of git diff incorrect.
Change-Id: Id2286147529f1072fe4ceff3fc5200aeb30267a1
Related-Bug: #1264422
Related-Bug: #1410434
This is a forward port of the tool we used to cap stable/juno
requirements. Save a copy of it in master so its available when we are
ready to cut future stable branches.
pin all global-requirements with the version found in pip-freeze
along with a tool to generate the new requirements file
Issues:
* Some versions are only apt-get installable (suds 0.4.1)
* Not all packages are installed in our standard dsvm-tempest env
* Some versions are lower then the minimum requirement we previously had
because python is awful (libvirt-python)
* Doesn't pin transitive dependencies
* library versions can vanish from pypi and still break us
* Grenade and tempest-full pip-freezes are different and do not work with
each other, so some tweaking is required.
Taking the installed library version from pip-freeze and use that as a
version cap.
Previously used pip-freeze from a tempest-dsvm-neutron-full job.
Change-Id: Iaf48bb069fdd7a19d614ce44b86abd9977c5f0c0
Since I8e453110655c0e74ff81b4cdc796c4935c75a553, we don't generate pbr
wheels from git, so there is no need for this either.
Change-Id: I0c70735556d1da68924518b9deb13f4ed082a79d
This adds a test to try to install all of the global-requirements.txt
into a venv to see if it works. If we can get this functioning, it
will help determine ordering issues and compatibility between all
components at an early stage.
Change-Id: Id147a7b31f96650159f5178ac6dbeec2736d73f6
