We would like to run the basic sanity testing for oVirt using lago on jenkins. We will supply link for engine/vdsm/any-other-package-built by lago, and we want the test to run on that patch. We would need that for master, and 3.6.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
This has two sections, and not all of them are really related to lago (but hopefully we can add a plugin to do it) * building rpms from a patch (now that we have standard ci, it should be easy to be able to pass any stardard-ci project) * Using those rpms to create the repo that is passed to the vms BZ#1279962) * Running the basic_suite (BZ#1278491 + another for master branch)
hehehe, that's how I count :)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Changing assignee, please feel free to re-assign to relevant teams.
In progress: 3.6 is pending a fix for network issue for ovirt: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_3.6_system-tests/ Currently runs nightly. 4.0 is still in progress (see attached patch for ovirt-system-tests): http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-tests/
3.6, 4.0 and master are working. Waiting for a decision if to enable API V4.
It might be possible now to use the new experimental flow that deploys any new built package into the experimental repo and run verification on it via OST. However, today it runs on merged commits to ALL projects, we'll need to think how to enable it per patch, but manually, via jenkins job or HOOK in gerrit.
OST is not using bugzilla for tracking for a while, closing outstanding open bugs. If you wish to follow up on this issue please do so at https://github.com/oVirt/ovirt-system-tests