My current Jenkins installation runs in the background with a user that has
no shell and no GUI
So far that is the normal setup I have read around. However my latest unit
tests for drag/drop operations are failing because such user does not have
a running pasteboard service. I am still trying to find out how start that
service. Googling around I found this:
> nohup /System/Library/CoreServices/pbs &
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.
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.
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?
thanks in advance
Francisco Garcia
