386ddc2268
The owners of maven.research.rackspacecloud.com/ seem to have introduced a 301 redirect permanent from http -> https URLs on around Jan 10th. This has broken the master/trove check builds since that time. Maven, when running in the infrastructure CI environment, fails to follow these redirects. This code change simply refers to the maven software repositories using https URLs. Local testing of this change against Tesora's downstream CI found that it may be necessary to purge the broken/cached file from the bare-trusty CI build machines ala: rm /home/jenkins/.m2/repository/com/rackspace/cloud/api/wadl-tools/1.0.9 (continued..) /wadl-tools-1.0.9.jar Closes-Bug: #1412949 Change-Id: I2dece05c74ad18a96fa05791e368ff7283a5e4e5
Trove
Trove is Database as a Service for Open Stack.
Usage for integration testing
If you'd like to start up a fake Trove API daemon for integration testing with your own tool, run:
$ ./tools/start-fake-mode.shStop the server with:
$ ./tools/stop-fake-mode.shTests
To run all tests and PEP8, run tox, like so:
$ toxTo run just the tests for Python 2.7, run:
$ tox -epy27To run just PEP8, run:
$ tox -epep8To generate a coverage report,run:
$ tox -ecover(note: on some boxes, the results may not be accurate unless you run it twice)
If you want to run only the tests in one file you can use testtools e.g.
$ python -m testtools.run trove.tests.unittests.python.module.path