git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git issue with connection keep-alive

From
MKMick Ken <micks80@gmail.com>
Date
Mar 18, 2011, 14:59 UTC
Message-ID
<AANLkTik==xnTxhOY-CoE5_oNkE-gdfSDBzBOgOgJGTbt@mail.gmail.com>

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
Message 1 of 1 in “Git issue with connection keep-alive”
  1. Mick KenMar 18, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.