|
||||||||
|
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.
It has been years since I last played with PackageMaker but I believe it was possible to build a package that will query if you want to install for all users or for current user only. If all users is chosen, the installer will prompt for admin password. It might be possible to determine which kind of installation happened in a post install script and place the launchd plist file in a location that either makes Jenkins be a launch daemon or launch agent.
However, I think it would be rude to unconditionally configure the current user's account such that after login he is immediately presented with the login screen again. It should at least be configurable (= ask the user) but how to do that with PackageMaker... I have no idea.
Actually I am really tired with PackageMaker. I believe a better user experience is achieved by creating an application, a single icon the user drags where he wants and runs by double-clicking. The application can then have a conversation with the user or present a rich UI to configure and run Jenkins. If a launch agent or daemon is needed, the application can set those up.
So, personally, rather than fight with the limitations of PackageMaker, I would rather improve Jenkins.app. I'm happy to collaborate on it (pull requests are welcome.) Jenkins.app is my own project but if people feel it should be in the official Jenkins git repository, I can renew my request to accept it there.
I have kept it outside of the official Jenkins tree because I assumed most people were happy with the PackageMaker based installer which runs Jenkins as a launch daemon. It has it's problems but there are workarounds and plugins like the Xcode plugin which should provide some relief.