oVirt CI Jobs running ovirt-system-tests¶
One of the main benefits of OST is using it in a CI environment, where you can catch regressions before a release
Currently the oVirt Jenkins server has a few jobs which run ovirt-system-tests on various flows per version.
These jobs are using oVirt packages which are built per commit and published nightly via the publishers jobs
Note: since the experimental jobs are running on newer packages, these jobs might be obselete soon since they are running on non-verified published RPMs.
Trigger/Frequency: Running on each OST patch, using latest.tested oVirt experimental rpms(see next section for info)
The ‘check-patch’ OST job is using the ‘standard CI’ to run the OST suites on each new OST patch.
Usually the job will run on the updated suite which is modified in the patch itself, but if any of the ‘common’ files
will be changed, all ‘basic’ suites will run as well to make sure a regression wasn’t added to a common file.
ovirt experimental jobs¶
Link: ovirt experimental jobs
Trigger: Running every time a new commit is merged on ANY oVirt project. (Usually will run on a few commits due to resource limitation).
These jobs are triggered by each ‘build-artifacts’ job in CI which created RPMs for a specific oVirt project.
These rpms are being deployed to a temp repo by the ‘deploy-ovirt-experimental’ job and merged into latest nightly repo using repoman.
Once the repo is ready with the new RPMs, the ‘test experimental’ job is triggered using the given repo.
If the tests pass then a new repo is being publised under latest tested repo,
for e.g for oVirt master latest master tested