On Sat, Feb 24, 2018, at 7:25 PM, Michal Schorm wrote:
So far I've seen 2 options: direct invoke "# ansible-playbook tests.yml" or runing VM from downloaded qcow2 image
Certain tests could break my system so I'd like to not running them in somehow isolated environment.
I run almost everything in containers (not mock, which should really only be used for building RPMs for compatibility); we have much more actively developed container technology for general purpose use. I'm in the process of switching from docker to podman myself.
See this talk from Devconf.cz 2018:
Sanja Bonic and Colin Walters: You want a Clean Desktop OS? Containerize it. Youtube: https://www.youtube.com/watch?v=a4IPWlfkJSo Slides: https://fedorapeople.org/~walters/2018.01-devconf-desktopcontainers/#/
Part of the whole set:
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Janu...
Something like `standard-test-roles` is a great example of something you don't want in the critical path for updating your host system. You don't want running it to accidentally somehow start installing packages on your host if Ansible picks up the wrong inventory, etc.
I run tests in my dev container, and it works fine!
Also, once you've gotten pretty far in containerizing your desktop (or server), we also have a fully transactional hybrid image/package system for the host side.