[ https://ovirt-jira.atlassian.net/browse/OVIRT-1476?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1476: ------------------------------------- Don't worry its pretty easy to set things up. The main idea of oVirt CI is that you write some shell scripts to set what you want to test, place then in certain locations in your source repo and then the CI system calls them in response to action you make on your source code (e.g. submit patches, merge them, etc.). For a longer overview of the CI-Standard which describes how the CI system works: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standa... So we need to decide of few things: # what are we going to test in CI. We don't need to decide everything up front though, we can start with simple stuff and add more over time. # When are we going to run tests, we ran run thing when patchsets are created or after merge. We have all kinds of functionality around building and delivering artifacts, but I guess that is less relevant for Ansible. One interesting thing we can consider doing at some point is to have the CI system trigger Ansible on production servers after patches are merged. We will probably need to finish OVIRT-894 first so we can make credentials for accessing servers and decrypting password stores available to the CI system. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)