Pypy is not tested in OpenStack anymore,remove the job.
in 'victoria' cycle, we should test py38 by default.
and remove redundant python env.
Change-Id: I8389799ebf2eaa95324b1dc532ef4398ee3094da
The repo is Python 3 now, so update hacking to version 2.0 which
supports Python 3.
Fix problems found.
Change-Id: I81cf5e317bb2f791888e75d87cfd27dfdd2b5f96
This is a mechanically generated patch to add a unit test job running
under Python 3.6 as part of the python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I48b1eda5ac2960fb13eaba39550d5ae3bc567281
Story: #2002586
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I1c4aaa0e0909f5272ab970950e3d21662dee2227
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Id03d28442b998624153e048ad9a621f31dbdb7d2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I673d98410d124d082272a7ba23836eb2e818f3e9
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: I21b90d9976d410d92194ab292c11bf972af1479c
* checkout one commit before the latest and check coverage
* check coverage with the latest commit
* all new lines must be tested
This functionallity essentially compares the current change
with the master branch, since the coverage job runs always
for only one change.
Change-Id: I59b03d5c5e69a36b5fac9fef0576a29a885a5bba
Partially-Implements: blueprint magnumclient-ut-coverage
Many deprecations are triggered early (on imports, for example).
To make sure all DeprecationWarning messages are emitted we enable
them via the PYTHONWARNINGS environment variable.
Change-Id: Ic523b37b39c33746adc372b2f20f7d211ac76dd8
Openstack infra now supports upper constraints for
all jobs. Updated tox.ini to use upper constraints
for all jobs.
Change-Id: I2c47f1a19c61a2b2034cf38100b87ddc62a93cfe
Closes-Bug: #1614117
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: Idafad48f97dc4ddcb63d217aa64f61cf236a7833
This will force pip install to use the upper-constraints.txt specified
version of pip modules. When you don't do this, you are out on the
bleeding edge and become unstable everytime some python library in the
world changes in a way that you don't expect.
Change-Id: I175240a59ee7ee9562db96ddf73d402c703f8e20
Closes-Bug: #1563038
This patch removes the bandit.yaml and just uses whatever Bandit
defaults with in the scan. This cuts down on the maintenance of
the burdensome bandit.yaml file.
This patch also changes the severity level of the scan to just
medium and high issues.
Here are the results without the -ll to exclude low severity:
http://paste.openstack.org/show/489898/
Change-Id: Ia063db516175f518cfa1c68902b8b74734f294c0
The non-voting bandit job is running stable, let's make it voting now.
Run security linter bandit as part of pep8. Pep8 is the usual linter
target and thus let's use it there instead of starting another node for
this short-running job.
Change-Id: Ia6183592f4623e62b1882b2ee549ba3c35f823fb
Once we add debug testenv, we can use "tox -e debug" to debug test cases
when tox is running. Then tox will use oslotest which really debug our
test cases. Only we should do is insert pdb into code.
It's easy to use.
the same in magnum:
https://review.openstack.org/#/c/266020/
Closes-Bug: #1534030
Change-Id: I63ea8086e269b4ecacb7f7e337f1adf2a869db94
To solve the problem of "db type could
not be determined" on py34 we have to run first the py34 env to, then, run
py27. This patch puts py34 first on the tox.ini list of envs to avoid this
problem to happen.
Change-Id: Ie8d7eba53fd3e67d6090c6b54af765596c1497bc
Closes-bug: #1489059
"Python 3.3 support is being dropped since OpenStack Liberty."
written in following URL.
https://wiki.openstack.org/wiki/Python3
And already the infra team and the oslo team are dropping py33
support from their projects.
Since we rely on oslo for a lot of our work, and depend on infra
for our CI, we should drop py33 support too.
Change-Id: I41d992d3e10d6cee8f215027092e5a1a5612d7be
Closes-Bug: #1526170
With this patch it will no longer be required to write each
single proxy variable. It will let pass more variable just
in a single line in future if we add more env variables.
for example *_proxy will get all variables like http_proxy,
https_proxy, no_proxy, any_proxy etc.
Change-Id: Id22d76be8ec165236e1f35f58a8e5617d0355281
as of mitaka, the infra team won't have the resources available to
reasonably test py26, also the oslo team is dropping py26 support
from their libraries. sine we rely on oslo for a lot of our work,
and depend on infra for our CI, we should drop py26 support too.
Change-Id: I8c1e5765228382c9982883320568fe729d0c35f8
Closes-Bug: 1519510
We remove old bandit special version txt file and include it
in test-requirements.txt to make sure it can updated by global
automatically.
Change-Id: Icd51df9baffb3e881a0f355423f56a1321b27ac3
Because python creates pyc files during tox runs, certain
changes in the tree, like deletes of files, or switching
branches, can create spurious errors.
Change-Id: I77f144fc681eadcf8fd7fe735753090e3ebc6084
Closes-Bug: #1368661
Python 3.4 changed some of the output from argparse and the
handling of default func and command behaviour; this patch
deals with both < and >= 3.4 behaviour.
Change-Id: I27983f7b06fc16aeedb98a4b36f7ff9a451706ec
Closes-Bug: 1496805
When a development environment is under a proxy, tox is failed even if
environment variables of the proxy are set.
This patch fixes this problem.
See Also: https://review.openstack.org/#/c/191600
Change-Id: I0045cb2253a4d102196fdab277462891a886fe3a
Co-Authored-By: Yuiko Takada <takada-yuiko@mxn.nes.nec.co.jp>
Closes-Bug: #1465086
Add bandit support for python-magnumclient executed via tox. The
idea is to gate on bandit once we work out the kinks. In the short
term, we will have an experiemtal job that can be run manually. After
that it will be added as a non-voting check job. Finally it will be
set as a voting check/gate.
Change-Id: I14d037cf611ea6efa9f8271e6e120cd11b764dc4
Partially-Implements: blueprint gate-bandit
Users can use these commands to add/remove/update bay attribute(s):
magnum bay-update <bay_id> replace <path=value>
magnum bay-update <bay_id> add <path=value>
magnum bay-update <bay_id> remove <path=value>
For example, this command updates the node_count attribute of a bay:
magnum bay-update 0aab40ba-3f48-4e6e-88a6-247be18b9711 replace node_count=1
Change-Id: If003beaca8e7e8bbdff2cf24d2810b0db9efdf41
Implements: blueprint update-node-count
Implements the boilerplate project setup. After this commit, I'll
import this project into stackforge, and we can continue development
from there.
The rest API identified is that of the work Eric put together initially
including bays, pods, and container objects.
Zuul