mitogen/.ci
Steven Robertson a6c293d100 try running ansible_mitogen 2.10 tests with python3 2020-09-22 19:47:18 -07:00
..
soak .ci: import soak scripts. 2019-02-18 18:01:54 +00:00
README.md .ci: add verbiage for run_batches() too. 2019-02-10 02:40:14 +00:00
ansible_install.py add missing collections 🤦 2020-09-20 18:12:58 -07:00
ansible_tests.py ansible.posix.synchronize isn't being loaded in tests but is locally, reducing v count to get around azure devops scroll bug 2020-09-20 21:11:04 -07:00
azure-pipelines-steps.yml revert python3 setup + add TODO; python3 tests aren't working now but python2 is EOL so they should work soon 2020-02-25 12:57:01 -08:00
azure-pipelines.yml try running ansible_mitogen 2.10 tests with python3 2020-09-22 19:47:18 -07:00
ci_lib.py Merge devel/290 @ 79b979ec8544ef5d8620c64068d4a42fabf50415 2019-11-02 16:46:59 +00:00
debops_common_install.py add missing collections 🤦 2020-09-20 18:12:58 -07:00
debops_common_tests.py issue #482: ci: add stray process checks to all jobs 2019-08-09 20:19:16 +01:00
localhost_ansible_install.py removed duplicate install and added debug dump of collection loading to see what tests are doing 2020-09-20 21:35:35 -07:00
localhost_ansible_tests.py any amount of v is too much v, even when viewing tests in raw log file mode 2020-09-20 20:02:50 -07:00
mitogen_install.py adding interpreter_discovery tests to ci 2020-02-18 15:48:46 -08:00
mitogen_py24_install.py Merge devel/290 @ 79b979ec8544ef5d8620c64068d4a42fabf50415 2019-11-02 16:46:59 +00:00
mitogen_py24_tests.py issue #477: add mitogen_py24 CI test type. 2019-01-26 22:00:30 +00:00
mitogen_tests.py issue #482: ci: add stray process checks to all jobs 2019-08-09 20:19:16 +01:00
prep_azure.py issue #587: disable SSH key setup, it breaks unit tests 2019-05-27 22:33:02 +01:00
spawn_reverse_shell.py issue #587: import spawn_reverse_shell.py script. 2019-05-27 20:14:36 +01:00

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 _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.