This patch removes hard-coded Python path in karma.conf.js
to fix the npm jobs because now these npm jobs run on
debian-bullseye and py38 are not available there.
Change-Id: I7474bfc60f503ab5b4a278e0f835cc088ec911a7
Previously the lint test was failing to run because there was no configuration file for it. This patch adds the .eslintrc file and fixes the found lint issues.
This patch also adds tox environments to run the lint and karma tests.
Change-Id: Idcef4c3ce4e9455acceed645c2530355989a7ee2
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I551f938a979c5921f204eca24fb3d16b9d47776d
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
Also removing the hacking and other related dep from lower-constraints file
as theose are blacklisted requirements and does not need to be present
there.
This paatch also update minimum tox version in tox.ini file.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Ia995caec9c4a0217be523c3179bfee85c1b6f7f8
Python 3.8 is now our highest level supported python runtime.
This updates the default tox target environments to swap out
py37 for py38 to make sure local development testing is
covering this version.
This does not impact zuul jobs in any way, nor prevent local
tests against py37. It just changes the default if none is
explicitly provided.
Change-Id: Iae572c8b08d7ad48495e759352205e217889d1be
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Update requirements, no need for python_version anymore
- Use newer openstackdocstheme and Sphinx versions
- Cleanup */source/conf.py to remove now obsolete content.
- Remove Babel from requirements, it's not needed for running.
- Update hacking to 3.0, fix problems found
Change-Id: I9eb22328474f52c2e225ae2a24c895c0e2bb63d7
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: I68ab10b4ac0e09b7d850e7c8f855a7e95c22d141
This commit adds a new tox target to build PDF documentation.
It's a part of community goal, see storyboard for more
information.
Change-Id: I66add3b35283fdb6337b6dad9d79e852984d471f
Story: 2006078
Task: 34824
Horizon defined a project template 'horizon-non-primary-django-jobs'
for django jobs. This patch use that template to run django jobs
here. For information please refer [1]
[1] https://review.opendev.org/#/c/681969/
Change-Id: I32a39fd2bde587a9891dea288026cc4518e89068
This fixes the tests by reuseing the more modern approach for
handling settings from the heat_dashboard.
Finally we remove the base designate jobs, as they do not
make use of the dashboard.
Change-Id: I53fd7bd0d01680c0bd59ad19365ceede0125050a
The current cover job is failing with the following error message
> manage.py test: error: unrecognized arguments: --cover-xml
Change-Id: I554300931d241fb82d4f204fd3fa120e37ee70b3
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: I985f87faefbe1b503b502c98acf0ed6003c587ad
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: Ic1713fae9a08c5ca234a02a9a403dec611a3cd3b
Replace django.core.urlresolves with django.urls
(In Django 2.0) The django.core.urlresolvers module is removed
in favor of its new location, django.urls.
It was deprecated in Django 1.10:
https://docs.djangoproject.com/en/2.0/releases/1.10/#id3
Add py35dj20 job to test Django 2.0 integration.
Change-Id: Ie57d111c44c607884e5ed3be614d4acae5e06b7f
Install horizon from git in Openstack CI.
Update the tox.ini for this.
Change-Id: I5e6cedf27f06692f7a6c7b75e21b7cff22e061f0
Signed-off-by: Charles Short <zulcss@gmail.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: Iaceac55505b73a8153f13937598805dd8469fcec
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Python 3.3 is not supported from Mitaka, as per Infra.
This patch removes the support and update to py35
for the same. Updated in venv also.
Change-Id: Ida50a9b6415cfc19bdbe37b3f6a60dc4c7aca73a
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: Iff88d06033f998d5e1ab84cac00e40bf516cd6b3
Closes-bug: #1489059
manchandavishal