Solution was provided via 'build on demand' and adding ansible suite to the manual flow

@Ondra Machacek @Martin Perina can you verify you can run the ansible suite using the manual job?

created https://ovirt-jira.atlassian.net/browse/OVIRT-1585#icft=OVIRT-1585 and sent the patch.
I've also applied the patch manually, so the ansible suite is actually available now through the manual suite.

Hi Ondra,
It's not really possible to add what you're asking with the current way OST works in CI, since the OST job isn't building ( and shouldn't ) build any project, just test it.

The way to test PRs in Jenkins is to use the manual job [1] and custom RPMs, usually built by the 'build on demand' feature.
The blog [2] described how to do it, though we'll need to check if we support 'build on demand' for GitHub projects like ovirt-ansible.

We'll need to add the 'ansible' suite the the list of suites you can test using the manual job and to verify you can build from a patch, so you'll have a custom yum repo to provide the job to test.

@Former user can you help adding the ansible suite to the list of suites available in the manual OST Job?
@Barak Korren do we support 'build on demand' for GitHub projects? if not, then i guess 'check-patch' job can be used if the RPM is built there

[1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/
[2] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/