You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Alex Willmer 28e08ef94c ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests This reduces the number of jobs from 48 to 24. The Mitogen part of the test suite has been parameterized on the Linux container targets to be run against. Both the Ansible tests & Mitogen tests now use the same source of truth to control which targets to use: environment variable MITOGEN_TEST_DISTRO_SPECS. This replaces the two mutually exclusive env vars DISTRO and DISTROS. I've also removed vestgial traces of an unused env var MITOGEN_TEST_DISTRO. Parameterization adapted from https://eli.thegreenplace.net/2014/04/02/dynamically-generating-python-test-cases refs #1058, #1059		3 weeks ago
..
soak	.ci: import soak scripts.	6 years ago
README.md	ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests	3 weeks ago
ansible_tests.py	ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests	3 weeks ago
ci_lib.py	ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests	3 weeks ago
debops_common_install.py	ci: Extract container registry location into variables	1 month ago
debops_common_tests.py	ci: Extract container registry location into variables	1 month ago
localhost_ansible_tests.py	tests: Remove --limit when running Ansible localhost CI	6 months ago
mitogen_py24_install.py	ci: Move container registry authentication to an Azure Devops step	1 month ago
mitogen_py24_tests.py	ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests	3 weeks ago
mitogen_tests.py	ci: Reduce number of Jobs by parameterizing Mitogen Docker SSH tests	3 weeks ago

README.md

`.ci`

This directory contains scripts for Continuous Integration platforms. Currently GitHub Actions, but ideally they will also run on any Debian-like machine.

The scripts are usually split into _install and _test steps. The _install step will damage your machine, the _test step will just run the tests the way CI runs them.

There is a common library, ci_lib.py, which just centralized a bunch of random macros and also environment parsing.

Some of the scripts allow you to pass extra flags through to the component under test, e.g. ../../.ci/ansible_tests.py -vvv will run with verbose.

Hack these scripts until your heart is content. There is no pride to be found here, just necessity.

`ci_lib.run_batches()`

There are some weird looking functions to extract more paralellism from the build. The above function takes lists of strings, arranging for the strings in each list to run in order, but for the lists to run in parallel. That's great for doing setup.py install while pulling a Docker container, for example.

Environment Variables

MITOGEN_TEST_DISTRO_SPECS: a space delimited list of distro specs to run the tests against. (e.g. centos6 ubuntu2004-py3*4). Each spec determines the Linux distribution, target Python interepreter & number of instances. Only distributions with a pre-built Linux container image can be used.
- debian-py3: when generating Ansible inventory file, set ansible_python_interpreter to python3, i.e. run a test where the target interpreter is Python 3.
- debian*16: generate 16 Docker containers running Debian. Also works with -py3.
MITOGEN_TEST_IMAGE_TEMPLATE: specifies the Linux container image name, and hence the container registry used for test targets.