4 ms·
Le sigh, continuous integration of osx and iOS apps is near impossible using standard cloud providers. I would gladly take an osx geared towards the data center
by exabrial 8y ago
Le sigh, continuous integration of osx and iOS apps is near impossible using standard cloud providers. I would gladly take an osx geared towards the data center.
- landonxjames 8y agoWe have a pretty good CI setup for our iOS apps using (shockingly) Microsoft's TFS. Not sure about any other cloud providers, but I was surprised by how easy it was to get working on a MS product.
- johnnycarcin 8y agoI had a friend a few months back looking for a CI setup for iOS and they found the same thing. For anyone wanting to kick the tires, it is called "App Center": https://azure.microsoft.com/en-us/services/app-center/ https://azure.microsoft.com/en-us/services/app-center/.
- meddlepal 8y agoIn theory this should be possible on Google Cloud using nested virtualization or EC2 bare metal...
- loxias 8y agoIf you find me funding, I could give you CI for mobile app development, a decent MVP, in 3 months (which is me taking how long i think it takes and multiplying by 3) :P But, like a previous poster said, it _WOULD_ be in violation of Apple's ToS. So a legal budget would be required.
- meddlepal 8y agoWe actually need something like this internally for non mobile app reasons. We build telepresence.io at Datawire and macOS dev and testing is a huge pain. Interested in a job :) ?
- loxias 8y agoHeck, if it's just iOS development, it might be possible to do a cloud CI that doesn't violate the ToS. When I was building all my iOS apps from Linux, I wasn't using osx.... I was using cross compiled clang....
- tom_ 8y agoI use Travis CI for the OS X build of my open source project. I build for OS X 10.7 but it looks like you get a good set of other stuff, iOS included: https://docs.travis-ci.com/user/reference/osx/#xcode-version https://docs.travis-ci.com/user/reference/osx/#xcode-version I think you may have to pay them to use it for closed source stuff. Not sure about setting it up to run on-site or whatever. Setup was sort-of quite easy, because I just ignored their CI system, however it works, and made the build run the same Python script I already used on my own Mac to make .dmgs - but it was still a bit painful in places, as their deployment options had some limitations, and the documentation wasn't always clear. But the end result does what I'd hoped for: master gets built, packaged, and uploaded to web site; build branch gets built, packaged, and pushed as a GitHub release. (For Windows I use AppVeyor. Mostly similar experience, but one advantage: they'll host your build artefacts for you, though presumably up to some limit. Good for the non-release day-to-day builds, as I like to have a decent set of these but don't really care about keeping them indefinitely.)