oVirt Blog

oVirt Gamification–The oVirt Game You Didn’t Know you Were Playing

Gamification is the concept of applying game mechanics and game design techniques to engage and motivate people to achieve their goals.

It taps into the basic desires and needs of the users impulses which revolve around the idea of Status and Achievement.

To put it in other words, it is turning day-to-day tasks, the kind you might do at home or work, into a game which you can earn points, badges and compete with other people that are doing the same things.

oVirt & Gamification

You probably didn’t know, but this isn’t the first time […]

oVirt System Tests to the Rescue!—How to Run End-to-End oVirt Tests on Your Patch

Today, when an oVirt developer pushes a patch to review on oVirt Gerrit, various validations are triggered in CI via the ‘check-patch’ job, as defined by the project maintainers. Usually these jobs includes ‘unit-tests’, ‘db tests’, static analysis checks, and even an occasional ‘functional test’. While it might seem that it covers alot and gives a good indication that the patch is good to be merged, unfortunately it is not always the case.

The reason it’s not enough lies in oVirt’s complexity and the fact it’s a Virtualization project, which means the only real way to know if your […]

CI Please Build—How to build your oVirt project on-demand

All projects in oVirt CI are built today post merge, using the ‘build-artifacts’ stage from oVirt’s CI standards.
This ensures that all oVirt projects are built and deployed to oVirt repositories and can be consumed by CI jobs, developers or oVirt users.

However, on some occasions a developer might need to build his project from an open patch.
Developers need this capability in order to to examine the effects of their changes on a full oVirt installation before merging those changes.
On some cases developers may even want to hand over packages based on un-merged patches to the QE team to verify […]