Issue was fixed,
I can see jobs triggered on 4.1 branch,.

e.g:
https://gerrit.ovirt.org/#/c/71072/

Just a bit mess but should work.
We prefer to leave each project with its name but as long as there are different names, it's OK by me.

Not sure what you mean by "where they should be built"? Do you mean for what versions of oVirt they should be built? In that case this is my suggestion:

Git repository - RPM name - Where to build
ovirt-engine-sdk - python-ovirt-engine-sdk4 - 4.y
ovirt-engine-sdk-java - java-ovirt-engine-sdk4 - 4.y
ovirt-engine-sdk-v3 - ovirt-engine-sdk-python - 3.y and 4.y
ovirt-engine-sdk-java-v3 - ovirt-engine-sdk-java - 3.y and 4.y

Would that help? I mean, doing this isn't useful for me, I am suggesting it because I thought it would solve the issues that you experience in the CI environment. Maybe we should setup a meeting so that you can explain me better what are those issues.

So what do you suggest? can you layout the new repos/name you'd like to see for V3+V4 and where they should be built?

Having the project and the RPM named the same is a price that I would't like to pay. This has always been the case, even before the introduction of V4. The name of the Python SDK, for example was ovirt-engine-sdk, but the name of the RPM was ovirt-engine-sdk-python. For the Ruby SDK (which only has V4) the name is also different: the repo is ovirt-engine-sdk-ruby but the name of the RPM is rubygem-ovirt-engine-sdk4. We can't (or should not) force projects to adopt the names that the distribution packaging requires.