|
||||||||
|
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/d/optout.
If git uses curl, then switching to use curl to guess if command line git would block may avoid these self-signed certificate cases.
I'd love to see a pull request with that change proposed, including a set of automated tests to verify it is working correctly.
Currently, I'm working to create automated tests of some relatively simple authenticated access paths (https, ssh, github, bitbucket, local server, etc.). My tests won't check for a self-signed certificate initially, since I don't have a self-signed certificate installed on any of the git servers I use for testing.