On Nov 24, 2012, at 4:39 AM, frankgarcia <pub...@francisco-garcia.net> wrote:
> OMG! That link is so useful. Now I no longer fear the part of code signing, > UI Automation + Frank, Pasteboard, Spotlight... and you confirmed my gut > feeling that running Jenkins as a background user has several downsides. Most > of blog posts I read about installing Jenkins gave instructions to install it > as a background user alone. It was actually XCode that drove us over the fence. There are too many things that are different between the GUI version of XCode and the command-line version (e.g., xcodebuild), and some of those things simply cannot be done from the CLI at all -- at least, not so far as we can tell. E.g., things like key management for codesigning. If you're working in a non-iOS/OS X environment, then I'm sure that background mode is probably fine. But development for iOS and OS X assumes that you'll be using the GUI tools, and there's all sorts of wacky fallout that happens when you don't -- like #include paths that are different between XCode 4 and xcodebuild (which works more like XCode 3, I'm told), so that you have to modify your project files to include user header search paths that are appropriate for both. Development for the iOS Simulator is also different from development for the Device (i386 vs. armv7 architectures), and that also requires things like different user header search paths. I can't tell you how many pull requests I have in against the various projects we're supporting, just because all the developers up until now have been using GUI tools, and I'm having all sorts of weird problems they've never seen before. So, I get to find the "bugs" and then create fixes that get uploaded to my forked copy of the repo, so that I can send them a pull request to make their code build correctly under Jenkins. > I was not that serious about using my own account. I assume you guys have a > unique normal OSX user for Jenkins alone. On our system, we end up installing well over a hundred Ruby gems and other tools, and trying to do those as a "normal" user is a pain. We created an organizational user that is also an "admin" account, so as to reduce the pain level somewhat during the process of installing the stuff that needs to be installed. YMMV, of course. > While I spice up my Jenkins setup, I wish you next week full of non-fail > tests commits. Thanks a lot! We're still in the process of getting our CI fully online and in production, but we're close. Good luck with yours! -- Brad Knowles <b...@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
