Previously heat-dashboard unit/integration tests always run
the whole set of tests and there is no way to run a specific test.
{posargs} mechanism of tox would help us.
Change-Id: Ia37a2586a9207180c5f3ed85141b2916468f18b8
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build
- Use newer openstackdocstheme and Sphinx versions
- Cleanup */source/conf.py to remove now obsolete content.
Change-Id: Icf69fa99ed77a0935062ee4fc8e9c6a195b381e5
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Update local hacking checks for new flake8.
Remove hacking and friends from lower-constraints, they are not needed
for installation.
Change-Id: Ib6f30427e736ff488598e80e87ce0a8b39e92f33
horizon recently switched from the third-party mock to unittest.mock.
This breaks heat-dashboard unit tests somehow.
We no longer support py27 and we can use the standard library
unittest.mock module. Rather than investigating the cause of
the failure, it would be nice to switch to unittest.mock.
horizon dependency is updated to 18.3.1 as unittest.mock is used
since 18.3.0 and 18.3.0 has an issue that it always requires pytest.
lower-constraints is updated to match horizon requirements.
hacking local-check-factory is disabled temporarily due to
the incompatibility with hacking 2.0 or later.
https://review.opendev.org/#/c/715690/ will recover it.
Change-Id: I517d6d7d36410c64bf48ad958b3e2115725a6491
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: Ie197efeb0080c5ad7f223823ff8b1888ff7dc0de
Change I95c81cfd6ab9bc7384c585ef5aa625dad9a57caf added a change
to temporarily disable the tox version check for testing - revert this
part.
Change-Id: Ife42a20edbfd9049e9e1e12e51257004e0711258
assertItemsEqual was renamed to assertCountEqual in Python 3, and the
testsuite is failing now - rename it.
See also https://six.readthedocs.io/#six.assertCountEqual
This unbreaks the testsuite.
Change-Id: I95c81cfd6ab9bc7384c585ef5aa625dad9a57caf
Horizon defined a project template 'horizon-non-primary-django-jobs'
for django jobs. This patch use that template to run django jobs
here and also fixes failed test cases for django2.2 support.
For information please refer [1]
[1] https://review.opendev.org/#/c/681969/
Change-Id: I3ab81402633b9abe39e49c3921585db992050540
This commit adds a new tox target to build PDF documentation.
It's a part of community goal, see storyboard for more
information.
Story: 2006083
Task: 34856
Our cgit instance will be going away and opendev.org is the new
preferred URL for browsing our git repos. Redirects will exist for the
foreseeable future, but it's more efficient to just go directly to the
new locations.
Change-Id: Ia84b464390dbbaaba4c87c4032f5fd21a529f412
Co-Authored-By: Vishal Manchanda <manchandavishal143@gmail.com>
In Train, we will use python 3.6 and 3.7 for python3 runtime
in our gate jobs [1]. This commit drops python 3.5 and adds python 3.7.
Redundant entries in tox.ini are cleanup along with python3.5 removal.
[1] https://governance.openstack.org/tc/reference/runtimes/train.html
Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Change-Id: Ideb2e7f6e7e3bd0986e5f6d400912a3e4e392e14
This patch adds basic tests to verify that heat-dashboard is
installed and could be opened.
heat-dashboard-integration-tests job is added in a
non-voting mode.
Depends-On: https://review.openstack.org/634712
Change-Id: I2550d6fcd1ce4e05502f247e227aaec05e762fcb
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: I981fa8d52800d24a5007f369ca6df4ffca9be0cb
Django 2.0 is now used in tox py35 job, so there is no need for
py35dj20 job. Instead, Django 1.11 with python3 is not covered.
- py35dj20 job is dropped from tox.ini.
- python3-django111 is added to tox.ini.
python3 is specified to basepython to avoid a specific python version.
- .zuul.yaml is updated to consume horizon-openstack-tox-python3-django111
and drop horizon-openstack-tox-py35dj20.
Change-Id: I90485a472edb5d2446c7e1bc08554fec72b307a0
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: Ic5fa4edff518a453941ec3d288f7a859adccec76
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Instead of using tox-install.sh, we can install horizon and neutron
now directly from pypi - or use the current branch in CI system using
tox-siblings.
Update tox.ini for this change and add horizon to requirements file.
Change-Id: I898fb222f5b36714c61e60c222e8b57ddea99df6
To enable translate job correctly, deleted heat-dashboard/locale
directory and updated babel-django.cfg accordingly.
Also fixed tox.ini which included wrong commands for docs build.
Change-Id: Idb7996ded645a8bc8bcb3b7eb08c8754a8492873
pip_install.sh is renamed to tox_install.sh to align with other projects.
The tox_install.sh here behaves a bit differently than the others, which
is causing some problems when trying to rework some of the shared gate jobs.
Align it to the form used in other repos.
Change-Id: Ie35d2b33f4bfaa8383c7af9e5ca489b61f7da073
Add .zuul.yaml file to make sure more flexible zuul job controll by
heat-dashboard team members, apart from project-config repo.
We will keep basic & common jobs in project-config repo,
also heat-dashboard repo will have specific jobs like as multi django
ver jobs.
Change-Id: Ia9084b10bf4bb1941e0eb21b51798c2090b459cc
To ensure project imports are placed after third party import,
we need to specify application-import-names.
Previously flake8-import-check checks only standard imports or not.
Change-Id: I9beb2105f686dc7d9aebfce8e21c5e182698e2fe
doc8 is a linter for documents and used in openstack-manuals.
It is better to enforce document linters for simple checking.
The current rules are really simple like:
- line length check (80 chars)
- new line at the end of file
Change-Id: I3810df521068ffc97e25a5fc56b72397bf9783bc
py27dj18 currently uses Django 1.10 (from upper-constraints.txt).
The Django version should be specified explicitly.
Change-Id: I23a6dda4da52a0758e2f3e3bff26795c161babb8
After updating code from actual branch we still use old *.pyc files.
It can give an unexpected result, for instance, a lot of tests are
broken due to unknown reasons.
This patch fixes this issue.
Change-Id: I3bdbad9748dc3d94d6d8914156604eab7ad877a0
In reviews we usually check import grouping but it is boring.
By using flake8-import-order plugin, we can avoid this.
This flake8 plugin is already used in tempest.
It enforces loose checking so it sounds good to use.
Note that flake8-import-order version is pinned to avoid unexpected
breakage of pep8 job.
Change-Id: I8ccd05eb70350a2441cc2a4d1eafc09ee690b83b
This commit enables the following two hacking rules
which are disabled by default.
* H203 Use assertIs(Not)None to check for None
* H904 Delay string interpolations at logging calls
Recently we clean them up in our code base and
it looks better to detect them automatically.
Change-Id: I4fb81b1d8e29c21aecd909a54d3294362fe140a2
Chrome in *nix environments requires the HOME and DISPLAY variables
to be set for Chrome to start properlyi when running the 'npm' rule.
The HOME variable is needed so Chrome can load up the user's
preferences. The DISPLAY variable is needed so it know what display
to launch Chrome into.
Change-Id: I84f4d1d47f065158e8f5bf5691c241061cc16aab
Closes-Bug: #1684321
niuke