Deal with CI issues

[orta]

Options:

• TeamCity - https://twitter.com/orta/status/568788102745079808
  • - https://github.com/foreflight/foreflight_build_agent

[ashfurrow]

If we could use something that allowed us to use pre-release versions of Xcode, that would help me with Eidolon wrt Swift improvements.

[orta]

http://staxmanade.com/2015/01/setting-jenkins-up-to-run-xctool-and-xcode-simulator-tests/

For anyone that’s interested, I think I found an answer to my Xcode 6 + CI woes via this blog post: http://staxmanade.com/2015/01/setting-jenkins-up-to-run-xctool-and-xcode-simulator-tests/ We recently migrated an older Jenkins C.I. server over to a newer...

andrewsardone [10:29 PM] When running Jenkins on your CI Mac, the key is to not only start up Jenkins as a LaunchAgent (so it can connect to your GUI iOS simulator), but also make sure your LaunchAgent is properly configured

andrewsardone [10:29 PM] i.e., do not set the SessionCreate key to true in your plist. In fact, completely omit that

andrewsardone [10:30 PM] Apparently if you omit SessionCreate, the launch agent will “[use] the global bootstrap namespace” – https://developer.apple.com/library/mac/technotes/tn2083/_index.html TN2083: Describes the most common problems encountered with daemons and agents, and suggests detailed solutions.

andrewsardone [10:30 PM] I suppose this is what allows the process to connect to the logged in user’s GUI and iOS Simulator

andrewsardone [10:31 PM] either way, with xctool this is seemingly proving to be more reliable than Travis CI, but it’s too early to tell

andrewsardone [10:31 PM] I like Travis CI, but for this project I’d like to get Jenkins working more reliably for some added capability (e.g., build artifacts)

[ashfurrow]

Should we close this? Seems like we've settled on Travis/Circle.

[orta]

yeah, I'm not going iOSDevOps.