[ctpide]

I’ve been using Concourse CI and it’s fairly light weight and has great declarative pipelines. Learning curve is not too steep and it has a command-line tool to update your pipelines. Maybe it’s a stupid suggestion, but you could connect the worker in that setup through ssh to a Mac for building, but of course that takes away some of the comfort, but you will have to run a dedicated build machine anyway.

Also, doesn’t Travis CI have macOS support ?

[mmanulis]

+1 to Concourse. Though if the OP needs OS X build support, there is no escaping needing a Mac box to run it on.

One can still run Concourse on a Mac Mini if one chooses, not that much extra work. This is the simplest solution but you will still need XCode Server last time I checked (been a while). I'm sure there are ways to hack around it, just a matter of time vs money question.

Both Travis CI and Circle CI offer Mac builds, so if one is willing to spend some money, that's an option.

Having had to run my own CI infrastructure, I'd rather pay someone else to deal with it. Especially if your deploys are tied to it, as once it breaks, and it will do it, your entire pipeline is down.

I ended up spending a good chunk of my own time dealing with failing builds or having a couple of people on my team be the point-persons for CI/CD infra.

[jakobegger]

I need to build and run tests on macOS, so I‘d need to circumvent the core principle of Concourse (containerized builds). I really don‘t want to work against my CI system...