On Nov 21, 2012, at 2:08 AM, frankgarcia <pub...@francisco-garcia.net> wrote:
> But that is not working for Mountain Lion. I am no longer looking for a > solution because now I believe this is not the real problem. I am planning to > add automated GUI tests for OSX and iOS, therefore I believe I will be having > more than just a pasteboard server not running problem. Correct, there are certain privileges that are dropped when moving from a "foreground" process to a "background" one, having to do with interacting with Spotlight, among other things. In Lion and Mountain Lion, we have not (yet) figured a way around that problem. > Should I create a normal system user for my Jenkins server? If so, I guess I > will have to setup everything so every time the server starts, a full blown > background user GUI session starts only for Jenkins. Any recommendations > about how to do the auto-login in the background. I could not find that > information and I am wondering what is the normal setup of OSX users for > Jenkins. We run our Jenkins server using Jenkins.app (by Sami Tikka, see <https://github.com/stisti/jenkins-app>), and that at least lets us do OS X and iOS UI testing with tools like frank-cucumber, as well as most of our integration tests for our server-side code -- minus the four tests that require interaction with Spotlight. > As quick/dirty solution I could just make Jenkins run under the same user I > normally log in into my server... but that seems kind of... non-ethical? I would say unwise, as opposed to unethical. If you get hit by a bus and your personal account gets deleted by your employer, the Jenkins system shouldn't be shut down as a result. You want to use organizational keys and accounts for all this sort of stuff (including for code signing), so that the system is not dependent on any particular "normal" user account continuing to be in existence long after the person themselves actually departed. -- Brad Knowles <b...@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
