@Liora Milbaum was the patch merged? can we close this?

@Emil Natan for build artifacts jobs, I don't see a reason why infra should be notifed and not just the maintainer or his team. same as check-patch emails.

It's not as simple as removing infra@ovirt.org from all aliases. Maybe there are people relying on receiving these and there are aliases which include only infra so you can't simple remove it. So maybe infra could be replaced with some other alias or single email addresses, but one needs to send email to infra with all details and propose plan to restructure these aliases.

git clone jenkins repo
cd jobs/confs/projects

git grep infra@ovirt.org
defaults.yaml: email-to: 'infra@ovirt.org'
ovirt-appliance/ovirt-appliance.yaml: email-to: 'infra@ovirt.org, yturgema@redhat.com'
ovirt-node-ng/ovirt-node-ng.yaml: email-to: 'infra@ovirt.org, yturgema@redhat.com'
ovirt-node-ng/ovirt-node-ng.yaml: email-to: 'infra@ovirt.org, yturgema@redhat.com'
ovirt/change-queues.yaml: email-recipients: 'infra@ovirt.org'
ovirt/system-tests.yaml: email-to: infra@ovirt.org
system/system_backup.yaml: mail_to: infra@ovirt.org
system/system_jobs.yaml: recipients: 'infra@ovirt.org'

I get them as part of the infra ML

Can you be specific? Which emails?

Build-artifacts jobs for example do not send emails anywhere...