12 Commits

Author SHA1 Message Date
b832048287 Switch to 2023.1 Python3 unit tests and generic template name
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I57d369e1e1a84a2685e3eb157699e1262c996400
2022-09-21 12:08:30 +00:00
6922e862f7 Add Python3 zed unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for zed.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Ib9a58c104aa0ec116ad86467b4d7b6ab4cdf7303
2022-03-23 16:06:53 +00:00
manchandavishal
8918bf751d Drop Django 2.2 support
Django 2.2 support was dropped. Django 2.2 ends its extended support
in April 2022[1]. Considering this, horizon dropped Django 2.2 support
and use Django 3.2 as default version of Django.

It also updates the python version from py38 to py39 for
"horizon-non-primary-django-jobs" and
"horizon-tox-python3-django" project template because py36
and py39 are now runtime for the Yoga cycle[2]. So I have updated it to
py39.

[1] https://www.djangoproject.com/download/
[2] https://review.opendev.org/c/openstack/governance/+/820195

Change-Id: I8886f12f7e51b721ac5123070086d5dcfefe4e72
2022-01-05 19:26:56 +00:00
Akihiro Motoki
9d1bb3626b Allow both Django 2.2 and 3.2 for smooth transition
I believe we need the following steps and it is what I did in past
when we bump the Django minimum version.

1. (already done) update global-requirements.txt to allow horizon to
   update requirements.txt to include Django 3.2.
2. specify the required Django version which includes both 2.2 and 3.2
   (at this point upper-constraints uses 2.2)
3. update upper-constraints.txt in the requirements repo to use Django 3.2
4. bump the min version of Django in horizon

(optionally) update non-primary-django tests to include non-primary versions of
Django. It seems you drops 2.2 support together when we support 3.2, so perhaps
this step is not the case though.

https://review.opendev.org/c/openstack/horizon/+/811412 directly updated
the min version to Django 3.2 which is incompatible with the global
upper-constraints.txt.
To avoid this, https://review.opendev.org/c/openstack/horizon/+/815206 made
almost all tests non-voting. I am not a fan of such approach and believe
there is a way to make the transition of Django version more smoothly.

---

This commit reverts the zuul configuration changes in
https://review.opendev.org/c/openstack/horizon/+/815206 and
https://review.opendev.org/c/openstack/horizon/+/811412.

horizon-tox-python3-django32 is voting now as we are making it
the default version.

Change-Id: I60bb672ef1b197e657a8b3bd86d07464bcb1759f
2021-10-26 09:57:06 +09:00
manchandavishal
7bfb56010d Bump Django version to Current LTS Version
This patch update Django version to the current LTS version i.e. 3.2.
Django 2.2 is going to end its extended support by April 2022[1].
horizon and all its plugins already support Django3.2 version, So
let's make this the default version. It also bump few other packages
version in lower-constraints.txt to make it work with Django 3.2.

Note: It also change 'openstack-tox-py38' job to non-voting
which I will revert in follow-up patch once this patch is merged.

[1] https://www.djangoproject.com/download/

Change-Id: I49e323b76ad2c2e680c3f133d0f219d850f7908c
2021-10-25 17:39:21 +05:30
66091d7b2f Add Python3 yoga unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I1e39e7abea536b5054557eb725069583b7504e0f
2021-09-23 14:14:34 +00:00
Akihiro Motoki
f3d2b9d540 Preparation for Django 3.2 support
This commit adds a non-voting unit test job with Django 3.2.

Jobs with Django 3.0 and 3.1 are dropped now.
They were introduced before Django 3.2 was released.
Django 3.0 reached EOL and Django 3.1 will reach EOL this December.
Django 3.2 is an LTS version so testing with Django 3.2 is enough.

Change-Id: Ic6ba0ea281b287b7f4762f92e2e81a6fd654da8f
2021-09-16 16:43:17 +09:00
Zuul
49b79a6f30 Merge "Preparation for Django 3.0 and 3.1 support (1)" 2021-07-29 14:52:45 +00:00
4310a9541f Add Python3 xena unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I03701fef6bcc985b59844817c588db5bbf6f881d
2021-03-30 19:02:48 +00:00
Akihiro Motoki
6a2635e32d Preparation for Django 3.0 and 3.1 support (1)
This commit enables non-voting unit test jobs with Django 3.0/3.1.

PendingDeprecationWarning is added to PYTHONWARNINGS in tox.ini.
PendingDeprecationWarning in Django 3.0+ includes deprecation warnings
on what will be dropped in Django 4.0 and they cannot be addressed
as long as we use Django 2.2.

Change-Id: I44e511ddc1d93fc3e2b68393b88c5f2cd1360854
2021-02-26 03:35:13 +09:00
106e713ee5 Add Python3 wallaby unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for wallaby.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Iac3273d68ffd93f3745d41fb31d2abd538d26711
2020-09-25 12:28:06 +00:00
Akihiro Motoki
ef1270167b zuul: break down config files into pieces
Our .zuul.yaml is long enough now. Let's split it into meaningful
pieces for better readability.

Change-Id: I53daefd95946d19d8f4f5845f0e83bf652c3a9aa
2020-06-24 17:33:06 +09:00