I've enabled Python and Ruby SDKs in Travis:

https://travis-ci.org/oVirt/ovirt-engine-sdk-ruby
https://travis-ci.org/oVirt/ovirt-engine-sdk

To have a Mac OS X slave we'll need buy/have it donated, Lets see of travis is good enough for now.
It should be possible to run Standard-CI scripts from travis to avoid some code duplication.

Not sure what permissions are needed exactly, but I think that those that have "admin" access to the "oVirt" organization can just go to travis-ci.org and enable/disable the projects, it is just a matter of flipping a switch. I'd appreciate someone with that access can do it for the Python and Ruby SDKs, as we had already more than one situation where Mac OS X users complained about build failures.

I also suggest to reconsider adding support for Mac OS X to Jenkins. I know that it isn't possible to have a Mac OS X VM, but maybe we could have at least one bare metal Mac OS X slave.

I replied on the other ticket, but if indeed we can't run MAC OS tests on existing infra and Travis is the only way, we should at least explore this option.

I don't know if it matters that the GitHub repos are mirrors of gerrit and if that should affect the integration with Travis, but if anyone from VDSM team wants to explore it,
we can give permissions in GitHub to the maintainer to check the possibility.

Note to infra team: there's a very similar request (OVIRT-757) to enable
Travis build from the github mirror of Vdsm. Please solve them together;
for Vdsm as well, triggering a build in check-patch would be
interesting.

Thanks for the suggestion to use "clang" Evgheni, that can certainly help, I will explore it.

I also see that Travis CI (https://travis-ci.com) supports building in Mac OS. I added a .travis.yml file to the Ruby SDK, and tested the build my personal github fork. It worked correctly. Is there any way to activate Travis builds for the oVirt mirror of the SDK that we have in github? That way at least the build will run after merging patches (before releasing). Do you know if there is any way to make Travis CI work directly from gerrit.ovirt.org, before merging patches?

We do not have any Apple hardware available at the moment. As it is illegal to run OS X on non-apple hardware we can't install it in VMs either.
As far as I know, OS X switched from gcc to clang so maybe it's possible to just try to build the gem using clang and test the result on our linux slaves. What do you think?