Hi, I am experiencing an issue with Git plugin in Jenkins. I have already posted the issue at the Jenkins mailing list but did not heard much in the last couple of days, so I thought of posting it here incase someone can help: Jenkins mailing list thread - http://groups.google.com/group/jenkinsci-users/browse_thread/thread/6f9d685d6aef4c49?hl=en In short, the issue is that when the Git plugin is trying to clone a repo it's failing but "Tortoise Git" on the same server is able to successfully able to clone the repo. After some debugging it looks like the Git calls are different, here's the internal Git call from Jenkins that's failing: C:\workspace>git clone http://<server_url>/project.git C:\Projects\ trace: built-in: git 'clone' 'http://<server_url>/project.git' 'C: \Projects\' trace: run_command: 'git-remote-http' 'origin' 'http://<server_url>/ project.git' Cloning into C:\Projects\... trace: run_command: 'fetch-pack' '--stateless-rpc' '--lock-pack' '-- thin' '--no-progress' 'http://<server_url>/project.git' 'refs/heads/ master' 'refs/heads/m3/master' Whereas, the tortoise git is just passing the "--progress -v" parameters and it's successful. Any ideas why the Git call from Jenkins is dropping the connection? Thanks -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html