Added support to mlbackend-python unit tests @ CI.
A new mlbackendPythonVersion parameter allows the mlbackend-python tag (from docker images) to be used. For example:
mlbackendPythonVersion = 3.0.4-python3.7.5
Empty means no mlbackend-python tests will be run
Some runs in testing job (of the core_analytics_testsuite only):
- master, no mlbacked version (11 skipped as expected): https://ci.moodle.org/view/Testing/job/DEV.99%20-%20Developer-requested%20PHPUnit%20(mlbackend)/6/
- master, mlbackend version 3.0.4-python3.7.5 (all run, as expected): https://ci.moodle.org/view/Testing/job/DEV.99%20-%20Developer-requested%20PHPUnit%20(mlbackend)/7/
- MOODLE_311_STABLE, no mlbackend version (11 skipped as expected): https://ci.moodle.org/view/Testing/job/DEV.99%20-%20Developer-requested%20PHPUnit%20(mlbackend)/8/
- MOODLE_311_STABLE, mlbackend version 2.6.5-python3.7.5 (all run, as expected): https://ci.moodle.org/view/Testing/job/DEV.99%20-%20Developer-requested%20PHPUnit%20(mlbackend)/9/
Once this is merged I will:
- Add support to the DEV jobs to this new parameter.
- Make mariadb PHPUnit jobs to run with the mlbackend-python tests enabled.