|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Re code signing: This is best handled by the Xcode Plugin. See https://wiki.jenkins-ci.org/display/JENKINS/Xcode+Plugin#XcodePlugin-Signing
Re UI Automation scripts (using iOS Simulator): Everything I have found suggests this requires that the jenkins process must run as an administrative user with elevated privileges. I do not know how elevated.
My suggestion is that we stick to a standard OS X .pkg installer that creates a launchd.plist within the Jenkins installation area, and provides the user with instructions to copy the .plist file to /Library/LaunchDaemons or to ${HOME}/Library/LaunchAgents bases on the user's needs. Alternately, a tool (a shell script so it could be run via SSH) that guides the user though making that decision could be provided.
Another possible suggestion is that a full (master) install of Jenkins should always be a LaunchDaemon (gets less privileges than the LaunchAgent) and that a Jenkins JNLP slave should be run (possibly on the same machine) for UI Automation. This suggestion is because the master listens for inbound connections, while a JNLP slave initiates its connection to the master, but does not listen for inbound connections.