Re: Do we or can we have Mac OS slaves in Jenkins?
Description
Opening a ticket.
On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand@redhat.com>
wrote:
> Hello,
>
> Part of the Ruby SDK uses native code that needs to be compiled during
> installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> many ManageIQ developers/users use Mac OS. In the past I had some issues
> with this environment, as the C compiler there behaves in an slightly
> different way than GCC. Those issues were discovered only when the SDK
> was already released. To avoid that I would like to have Jenkins jobs
> building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> slaves? If not, can we have them?
>
> Regards,
> Juan Hernandez
>
> –
> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3ºD, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
–
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
<https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>
Activity
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.
Thank you very much Barak. I agree, lets test Travis for a while before making any other change.
CC Travis CI integration for the Python SDK is now enabled. For future releases it would be good to make sure that the build in Mac OS X works before actually releasing the new version.
anything else is needed?
We agreed that using Travis CI is good enough for now, so this issue can be closed.
Assignee
Reporter
Blocked By
Epic Link
Priority
