|
||||||||
|
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.
@Mark Waite:
Thanks a lot for explaining why there is a connection from Java to the repository even if not JGit but the native git client is configured in Jenkins. This is pretty counter intuitive unless it gets explained.
But couldn't we achieve the same (i.e. find out if a password prompt would block the call) by making a call to curl?
My reasoning is that
a) AFAIK git uses curl, so if curl will work, git will at least not fail because of required but not supplied credentials
b) If the system administrator has made sure that native git will be able to connect to the repository (for example by providing HTTP/S proxy credentials in an environment variable) it will work for curl as well