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 e76eefb8be Fix miscellaneous spelling/formatting		3 years ago
..
soak	.ci: import soak scripts.	6 years ago
README.md	Abandon Travis CI We have no credits, and its a PITA to maintain two CI platforms. The tests running on Travis provide very little extra coverage vs Azure Pipelines alone	3 years ago
ansible_install.py	ci: Don't install pycparser and idna seperately	3 years ago
ansible_tests.py	ci: Reduce verbosity of Ansible integration tests	3 years ago
azure-pipelines-steps.yml	CI: Remove obsolete reverse shell historically used to debug CI	3 years ago
azure-pipelines.yml	ci: Reduce verbosity of Ansible integration tests	3 years ago
ci_lib.py	Fix miscellaneous spelling/formatting	3 years ago
debops_common_install.py	ci: Don't install pycparser and idna seperately	3 years ago
debops_common_tests.py	netaddr needs to be on the Ansible controller, not in target nodes	4 years ago
localhost_ansible_install.py	ci: Don't install pycparser and idna seperately	3 years ago
localhost_ansible_tests.py	ci: Reduce verbosity of Ansible integration tests	3 years ago
mitogen_install.py	ci: Don't install pycparser and idna seperately	3 years ago
mitogen_py24_install.py	tests: Authenticate to AWS Elastic Container Registry for `docker pull`	3 years ago
mitogen_py24_tests.py	issue #477 : add mitogen_py24 CI test type.	6 years ago
mitogen_tests.py	issue #482 : ci: add stray process checks to all jobs	5 years ago
prep_azure.py	tests: Tighten requirements.txt, due to new package releases	3 years ago

README.md

`.ci`

This directory contains scripts for Continuous Integration platforms. Currently Azure Pipelines, but they will also happily 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

VER: Ansible version the _install script should install. Default changes over time.
TARGET_COUNT: number of targets for debops_ run. Defaults to 2.
DISTRO: the mitogen_ tests need a target Docker container distro. This name comes from the Docker Hub mitogen user, i.e. mitogen/$DISTRO-test
DISTROS: the ansible_ tests can run against multiple targets simultaneously, which speeds things up. This is a space-separated list of DISTRO names, but additionally, supports:
- 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.