Hi folks,
Is there any automatized way to run the tests localy in Mock? 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.
Also, I'd use some safe way to develop such tests. Which will lead to broken system much more likely.
--
Should I expect this idea incorporated, or should I rather prepare some VMs? (lesser size tan 600MB each image)
--
Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat
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.
Hey,
My name is Daniel, I'm from oVirt's [1] CI team. We use mock to provide isolated environments for our tests/builds. For that purpose, we maintain a tool we call 'mock_runner' [2] that might fit your needs. Given a script to run and a set of configurations (which are mostly plain list files) such as repositories you need, packages to install inside mock and etc, will build the mock environment for you and run your script. For more info, you can refer to [3]
[1] https://ovirt.org/ [2] mock_runner code @gerrit https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=mock_configs/mock_runner.sh;h=0caa29ffcf5115837335bec8c3743d2272fc019d;hb=refs/heads/master [3] http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards...
On Sun, Feb 25, 2018 at 1:25 AM, Michal Schorm mschorm@redhat.com wrote:
Hi folks,
Is there any automatized way to run the tests localy in Mock? 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.
Also, I'd use some safe way to develop such tests. Which will lead to broken system much more likely.
--
Should I expect this idea incorporated, or should I rather prepare some VMs? (lesser size tan 600MB each image)
If you want to run your tests isolated once you have built your packages locally, you can try the PR associated with this issue: https://pagure.io/standard-test-roles/issue/106 -- Fred
ci@lists.stg.fedoraproject.org
-
Colin Walters -
Daniel Belenky -
Frederic Lepied -
Michal Schorm