Create Branch and User fields in ansible_suite job

Description

I would like to have following fields in ansible job[1].

  • branch (default: devel)

  • username (default: ansible)

So in OST[2], we can define which branch+ from which git repo, should be fetched,
with this we can test PRs.

[1] http://jenkins.ovirt.org/job/system-tests_ansible-suite-master/
[2] https://github.com/oVirt/ovirt-system-tests/blob/master/run_suite.sh#L212

Activity

Show:
Eyal Edri
August 8, 2017, 1:59 PM

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.

can you help adding the ansible suite to the list of suites available in the manual OST Job?
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/

Daniel Belenky
August 9, 2017, 7:18 AM

created and sent the patch.
I've also applied the patch manually, so the ansible suite is actually available now through the manual suite.

Eyal Edri
August 24, 2017, 9:18 AM

can you verify you can run the ansible suite using the manual job?

Eyal Edri
August 29, 2017, 1:30 PM

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

Assignee

infra

Reporter

Ondra Machacek

Blocked By

None

Components

Priority

Medium
Configure