|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Further to my previous comment:
The git configuration page runs 'git config --local', which will always require a workspace, but one doesn't exist (or hasn't been initialised at that point). That is why polling doesn't work too, as there is no workspace then either.
We could go down the route of requiring an initialised workspace, but that seems like a backwards step as the git client was recently changed to do a ls-remote and therefore not to require a workspace (e.g. see JENKINS-10131).
I've created a fork with the config set to system too - see https://github.com/pphillips-techphob/git-client-plugin/tree/config-system. I found that the Windows user that Jenkins is running as doesn't have a user home directory so therefore required that the configuration be stored in git home instead.