|
||||||||
|
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.
When running Jenkins as a service, using a dedicated user account here for is a must!!!
Under Linux you don't want to run your service as root user. Similar you don't want to run the Jenkins service on Windows under the 'System Account'.
And: YES, the pre-install script of that Linux rpm package does create the corresponding group and account named 'jenkins' for you. As well it registers Jenkins as service.
For the Windows installation package I'm not sure. If I recall correctly there have been packages out which registered the service to run under the 'System Account' - which may no longer be true ...![]()
We ugraded the up'n running Windows Jenkins environments only with replacing the jenkins.war.
But it's easy to check, under which account the Jenkins service is running under Windows (look into the Task manager![]()