|
||||||||
|
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.
That's a great result. Thanks very much. That says that the wrapper around the "git ls-remote -h" call is (incorrectly) returning null when it polls the remote repository. One work around would be to require a local workspace.
If you're still willing to experiment, I need you to login as the Jenkins user on your Jenkins master node, change to a completely empty directory outside of any git repository, and execute the command "git ls-remote -h your_url" where you replace your_url with the URL of your repository. I suspect it will report something of interest, though I'm not entirely sure what it will report.
I've also uploaded a minor addition trying to assure that the URL used by the plugin matches the URL you expect. If the git ls-remote command output does not surprise you, then download the latest change from that same branch, compile it, and install it. It will report the URL of the repository which git ls-remote is polling.