n/m saw it, so you're doing everything from YAML, so this is the kind of implementation I would call specific, a generic implementation would specify soemthing to put in the automation dir so nobody needs to know YAML...

which patch? I'm not seeing any patch linked here...

Not sure I understand, the current patch is as generic as it gets without any relation to getbadgets or gamification,
If its merged nothing will happen on CI (already verified) because the URL for the webhook is empty by default.

Only if you provide a URL as param from a project then its activated, for e.g for jenkins project:
https://gerrit.ovirt.org/#/c/68903/1/jobs/confs/projects/jenkins/jenkins_standard.yaml

The alternative is to create a new template for it and change multiple projects to use it if we want, which I don't see a reason for, if by default the plugin is not active.

The big question is if we want to have it generic, which will require extensions to the CI standard, and some thinking and perhaps some non-trivial Jenkins tricks, or, we just want to quickly support GetBadges.

Forgot to add the link to the game: https://ovirt-ovirt-engine.getbadges.io/activity

Of course it doesn't only have to serve GetBadgets, we can use it in the future to capture events from Jenkins from other systems,
one example will be a reporting system that can aggregate results into a cental datawarehouse which we can then create reports from.

any project which will want to use it need to pass the URL as parameter

Integration with GetBadges Gamification which is working nice until now with the GitHub integration, this will allow oVirt users/developers to get badges / points on having
successful builds ( or lose on failing builds ).

We already got positive feedback from developers on it, and adding another integration will increase visibility of the game [1] and hopefully make oVirt more fun to use/fix bugs/make ci happy.

Fedora has something similar which works well [1]

[1] https://badges.fedoraproject.org/

Why do we want this?