|
||||||||
|
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.
Could you check again with git-plugin 2.0.1 and git-client-plugin 1.6.2? The git-client-plugin credentials implementation is more mature now and has been confirmed to work over https with or without credentials to GitHub and to bitbucket.
There is a known bug ( JENKINS-20356 ) that the cloning with credentials does not work when Jenkins is running as a Windows service.
There may also be issues with self-signed certificates on https servers, though I don't have access to a server with a self-signed certificate for testing.