Ability to run as an Agent

[cowwoc]

Jenkins must run as an Agent (instead of a Daemon) if you need to run the iOS simulator. See http://9elements.com/io/index.php/continuous-integration-of-ios-projects-using-jenkins-cocoapods-and-kiwi/ for an explanation.

Please add a command-line option to install the service as an Agent.

[rhwood]

I think the following will need to be done:

• use a keychain other than the login keychain by default.
• ensure that security.sh does not attempt to lock or unlock the login keychain when running as an agent.
• provide an intelligent migration method from the login keychain to the new keychain (this could be done later).
• the installer needs to place the launch daemon plist in the correct place.
• ensure the installer, when installing the agent, and when run by the user that will use the agent, does not call sudo

[rhwood]

Actually just ensuring that when run as an agent, security.sh does not lock the keychain would obviate any advantage of not using the login.keychain (since it would otherwise cause confusion when configuring jobs on Jenkins).

[cowwoc]

I posted a description of how I believe this should be implemented: https://issues.jenkins-ci.org/browse/JENKINS-21237

[rhwood]

I'm actually thinking that I'm going to require that, to install as an agent, the account must exist already, and that the installer be run by the account that will run the agent, such that something like:
sudo -u agent-user install —agent
would force an agent-based installation for another user.

Maybe I ought to just prompt for the type of installation unless —agent or —daemon are passed to the installer…

I have another higher-priority project to work on the next couple of weeks before I get to this.

[cowwoc]

I'm fine with that (requiring the account to exist).