a64e966ab9
These are not part of the official testing regime (tests run for pull requests). I find them convenient for local development. Limitations - Python 2.7+ only. No Python 2.4, 2.5, or 2.6. - Requires Pythons pre-installed (e.g. DeadSnakes, pyenv) - No coverage of alternate controller OS (e.g. MacOS) The environments tested by default are py27-mode_ansible-ansible2.10 py36-mode_ansible-ansible2.10 py39-mode_ansible-ansible2.10 py27-mode_mitogen py36-mode_mitogen py39-mode_mitogen py27-mode_mitogen-distro_centos7 py36-mode_mitogen-distro_centos7 py39-mode_mitogen-distro_centos7 |
4 years ago | |
|---|---|---|
| .. | ||
| soak | ||
| README.md | ||
| ansible_install.py | ||
| ansible_tests.py | 4 years ago | |
| azure-pipelines-steps.yml | ||
| azure-pipelines.yml | 4 years ago | |
| ci_lib.py | ||
| debops_common_install.py | 4 years ago | |
| debops_common_tests.py | 4 years ago | |
| localhost_ansible_install.py | ||
| localhost_ansible_tests.py | ||
| mitogen_install.py | ||
| mitogen_py24_install.py | ||
| mitogen_py24_tests.py | ||
| mitogen_tests.py | ||
| prep_azure.py | ||
| spawn_reverse_shell.py | ||
| travis.sh | ||
README.md
.ci
This directory contains scripts for Travis CI and (more or less) 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_installscript should install. Default changes over time.TARGET_COUNT: number of targets fordebops_run. Defaults to 2.DISTRO: themitogen_tests need a target Docker container distro. This name comes from the Docker Hubmitogenuser, i.e.mitogen/$DISTRO-testDISTROS: theansible_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, setansible_python_interpretertopython3, i.e. run a test where the target interpreter is Python 3.debian*16: generate 16 Docker containers running Debian. Also works with -py3.