Project

General

Profile

Actions

Cleanup #49586

open

mgr/dashboard: perform matrix distro-release testing for tox tests

Added by Ernesto Puerta about 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
High
Assignee:
Category:
General - Back-end
Target version:
% Done:

0%

Tags:
dependency
Backport:
pacific,octopus,nautilus
Reviewed:
Affected Versions:
Pull request ID:

Description

Currently we only test Python code + pip-installed requirements for a single stack of versions (defined in constraints.txt).

We have recently faced several issues due to different versions, so we would like to explore the idea of testing some of the tox-envs (pylint, pytest unittests) under a combination of Distros (Ubuntu, CentOS) and Releases (Ubuntu 16, 18, 20, CentOS 7, 8).

As part of this issue, we should explore the following alternatives:
  • Manually updating constraints-{distro}-{release}.txt for each of the distros-releases supported and using generative tox lists. However that requires manually updating the dependencies and wouldn't have helped in this case.
  • Generating those constraints.txt files on the fly by fetching the package versions for every distro (via apt/yum/etc).
  • Using docker images for every distro-release to run tox inside from site packages (instead of pip-installed ones).

Each approach has their pros-cons (need of manual updates, increased runtime/resources overhead, ...).

Actions #1

Updated by Alfonso Martínez about 3 years ago

  • Assignee set to Nizamudeen A
Actions #2

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 146 to General - Back-end
Actions

Also available in: Atom PDF