|
||||||||
|
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.
I rarely run Jenkins as a service on any of the Windows machines I configure. Most of the products which I need to build and test are working from the assumption that if they are running on Windows they have access to the Windows Desktop. Access to the Windows Desktop is most directly available by running the Jenkins master and Jenkins slaves from a command prompt on the Windows Desktop.
I realize that there is a setting which allows a service to interact with the Desktop, but that is not the typical environment where my programs run. They are more likely to run on a real desktop, as real desktop programs.
There have been several bugs reported which have been related to Jenkins running as a service on Windows. I prefer to avoid those bugs by running on the Desktop.
I don't know why the git-client-plugin has this difference when running from a service or not. If I find a way to write automated tests of credentials in the git-client-plugin, that will probably also lead to a solution to JENKINS-20356. Until then, it will probably remain open as a bug.