In an attempt to make the proposal bot changes for requirements be
more meaningful make the update.py script return something that's more
user friendly.
Now by default the script will return the following to stdout on success:
Version change for: mox, mox3, testrepository, testtools
Updated project/test-requirements.txt:
mox==0.5.3 -> mox>=0.5.3
mox3==0.7.3 -> mox3>=0.7.0
testrepository>=0.0.13 -> testrepository>=0.0.17
testtools>=0.9.27 -> testtools>=0.9.32
Add a verbose flag that will provide much of the previous debug info.
Eliminate the giant dict dump of all the requirements files, as that
was largely impossible to make sense of, and rarely provided any
insight. During a devstack run you'll have git hashes for all the
trees, so can track down exact file contents if needed.
By making this the default stdout we can then capture and use this for
the git commit messages.
In order to make the test output matching human readable ignore the 80
column limit for the expected blocks via #noqa.
Change-Id: I85604db7bffafcd20bf3cc546fe3e5d7bda72193
This provides a new flag to update.py which allows for a "soft
update", which updates all the requirements found in g-r to the g-r
specified versions, but lets any unknown lines pass through as is,
without warning. This makes the tool usable for ecosystem projects
that want to test with g-r versions of the g-r specified dependencies,
but also want to be able to add their own dependencies above and beyond.
Change-Id: I1f195ef9ff1509659848e14ec9936ff6f66a6496
During sync, add a header to the requirements files warning anyone
against changing the order of the contents, especially against sorting.
Addresses-Bug: #1365061
Change-Id: I64ae9191863564e278a35d42ec9cd743a233028e
There was no easy way to check that the requirements in the
current commit overlap with requirements in the ancestor commit.
This change adds a tox env that when run compares the
global-requirements.txt with the parent commit's
global-requirements.txt. If the requirements for the packages don't
overlap it fails.
Run it with
tox -e versions-overlap-parent
Change-Id: I03bdead39760e9c13d6de4a33f8e5e788052323d
Closes-Bug: #1326504
oslo-incubator commit ad248f6 adds usage of the namedtuple_as_object
kwarg to simplejson's json.dumps.
oslo-incubator's test-requirements requires simplejson >= 2.0.9 but
namedtuple_as_object wasn't available until 2.2.0.
This is important for anyone doing keystone database migrations on RHEL
6.5 with simplejson since the migrations will fail if you don't have a
new enough simplejson (keystone is using this code now).
Change-Id: I59f4e9c42ad83a305d810e52e440ff51ff5b7f0e
Closes-Bug: #1361230
Currently pyzmq supports 2 branches with some API differences:
2.* - legacy branch
14.* - current branch
Due to historic reasons we bind pyzmq to an old API version.
In devstack we install latest version of pyzmq and not 2.* branch.
Cause of this I don't see any reason for us to bind pyzmq to such an old version.
Updating to latest version of pyzmq will allow us to implement zmq
driver in oslo.messaging that won't depend on eventlet and will be Py3
compatible.
Change-Id: I009e61303c01324de29ec78202621f50420d4d7f
Update to the latest heatclient version, which is needed for heat
to access some recent features such as software-config.
Change-Id: Ie442aed94efe4a3dafe708f603842f6ee3830416
there are non integrated projects in openstack that use devstack
framework for running jobs. They need a lever in their jobs to
tell the infrastructure that we won't enforce global-requirements
strict compliance on them. We'll still generate a warning so that
they know they are using requirements outside of OpenStack's
accepted list, but it will be non fatal.
Change-Id: Id90547e2fb0a5736385c9f31ba386e7c2e0616df
Don't silently remove dependencies not in global reqs, instead let them
fail installation.
Note: this assumes that devstack will terminate if this fails.
Change-Id: I23be4c2084e07a6b60b64347af9b4c5338b06ada
We don't need vim modelines in each source file, it can be set in
user's vimrc.
Change-Id: Ib2b5642b7d9051d4586419a6dd4785060cd59825
Closes-Bug: #1229324
Due to the fact that we'd like to keep pbr's requirements in sync with
global requirements we should disable syncing of setup.py for pbr.
* existing tests fixed by adding standard setup.cfg file;
* new test case added for syncing pbr project (with pbr like setup.cfg file).
Change-Id: Ibf5fcdad118fffb4fd5dd50c5d1decfa6f9a6479
This is the 2nd patch that upgrades the hp3parclient
to requiring the new 3.0.0 version for unit tests.
Change-Id: Ie78b03499b6ba53e75716ff1d4159424a7a82fae
The updated hp3parclient v3.0.0 is required for the new HP 3PAR
cinder driver and it's unit tests. This patch is the first in
2 patches that are need to land. We are breaking this up into
2 patches to avoid breaking continuous deployment.
First we'll update the top end to 4.0 in this patch. The
next patch will update the low end to 3.0.
Change-Id: I2d0f92b7d082637d55f4bbc7cac66c97aa73cfe0
This new version brings Python 3 support, leaner requirements and better
packaging. Python-keystoneclient needs this to be Python 3 compatible.
Change-Id: I85298e7b99cfb1abec42058e63ee419e46900cb4
The 0.7.1 release has a fix for the parse_querystring function, which raised a
TypeError on Python 3.3. See:
https://github.com/gabrielfalcao/HTTPretty/commit/5c6e776
This helps fix some tests on Python3.3 in python-keystoneclient.
Change-Id: If14a0afe9d42602e978377d6f6ee830affe0cc41
In Python 3, the map() function returns an iterator.
In Python 2, it returned a list.
Use list(map()) to fix the test_update/test_update_suffix errors
in py33 env.
Change-Id: I9d122fb5edf055ae0110e3a445d10733a817d7d2
Add mox3 dependency, mox is not python3 compliant so use
the mox3 port to help transition the testsuites to mock.
Change-Id: I2312b0bac69f8bc4d2d23b88a59a2e22f2073a9b
Signed-off-by: Chuck Short <chuck.short@canonical.com>
When we run update.py automatically in the devstack gate, we
have the issue that we are programatically changing files which
are actually git versioned. This makes lots of people sad pandas.
As this is all being done automatically we could actually update
the files with a suffix, then have devstack use that instead.
This will make developers happy, as they won't have to keep
resetting their devstack trees if they do development straight in
them.
Change-Id: I3d264f15ab7123f258f198b375b9667895c4104c
This allows us to pass through an exact line from
dev-requirements.txt as valid, if it's not exactly valid we'll
revert to the base requirement. This is needed so that projects
can keep development requirements in their tree.
Redo an if statement to make E125 happy....
Change-Id: I50a1292c321b7092ca1c7aeee5068f0828ece7b0
If a project isn't on pbr, then force-upgrading their setup.py will
be a categorical disaster.
Once glance and swift have finished moving, we can remove this 'feature'
but for now, it's a blocker.
Change-Id: I6ab41be97a2ff83c395861a95244d090c543d1fb
One of the points of pbr was ensuring that we had a consistent build
environment, but we still have boilerplate setup.py laying around.
Install the right boilerplate at update time.
Change-Id: If4b2e16b469171204270ace8144792e607cfddd7
... and in the darkness bind them.
This moves the contents of requirements.txt and
test-requirements.txt to a single file, global-requirements.txt.
This means that regardless of whether a requirement is in
either file it will get checked. This massively simplifies the
checking and upgrading of req and test-req files.
This also adds in a unit testing framework for the update.py
script to ensure it does what we think it does. This is
accomplished by making a fake tree with a set of req and test-req
files, running update.py, and ensuring the updates were made
that we expected. It includes testing for the oslo url case,
as well as test-requires.
Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
