2 ms·
I second the advice to go with a 3rd-party CI (although I am partial to TeamCity). This is especially because Apple's xcodebuild got way better in this release
by drewcrawford 13y ago
I second the advice to go with a 3rd-party CI (although I am partial to TeamCity).
This is especially because Apple's xcodebuild got way better in this release. It's the underlying deployment system behind the new CI, and in addition it can deploy things to devices now and handle all sorts of neat things that not even the best 3rd-party tools could do before. So:
> Unfortunately, xcodebuild doesn’t properly support test targets and application tests for iOS.
This is out of date, and if xcodebuild has given you problems in the past you should try it again.
- mackey 13y agoHas teamcity fixed it's Xcode runner yet for Xcode 5? I am using team city with shell scripts that hand off to "xcodebuild" and "xcodebuild -test | ocunit2junit" but for I would have liked to try out the runners. I prefer Jenkins overall, but our org uses team city and I would rather use something that has people devoted to managing it versus playing system administrator myself.