Rooba
/
mitogen
mirror of https://github.com/mitogen-hq/mitogen.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
mitogen/.ci
History
Alex Willmer 7bdec56a70 ci: One Tox environment per Azure job 
Should result in
- better isolation of faults
- easier retries of failed jobs
- quicker test completion, to to more efficient queueing.

This does not expand test coverage, merely rearranges the tests already run.
 		2021-11-17 22:12:52 +00:00
..
soak .ci: import soak scripts. 2019-02-18 18:01:54 +00:00
README.md ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +00:00
ansible_install.py ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +00:00
ansible_tests.py ci: Reduce verbosity of Ansible integration tests 2021-11-09 19:22:37 +00:00
azure-pipelines-steps.yml Support for Ansible 3 & 4 2021-11-12 22:10:53 +00:00
azure-pipelines.yml ci: One Tox environment per Azure job 2021-11-17 22:12:52 +00:00
ci_lib.py Support for Ansible 3 & 4 2021-11-12 22:10:53 +00:00
debops_common_install.py ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +00:00
debops_common_tests.py Support for Ansible 3 & 4 2021-11-12 22:10:53 +00:00
localhost_ansible_install.py ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +00:00
localhost_ansible_tests.py Support for Ansible 3 & 4 2021-11-12 22:10:53 +00:00
mitogen_install.py ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +00:00
mitogen_py24_install.py ci: Switch Continuous Integration to Tox 2021-11-10 20:17:53 +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

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

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