[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-22400

Re: Git timeout on other actions than fetch/clone Timeout support for JGit clone is first included in git client plugin 3.0.0-beta1. Prior to that version, JGit silently ignored timeout settings. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated an issue

Jenkins / JENKINS-22400

Git timeout on other actions than fetch/clone

Change By: Mark Waite Comment:

Timeout support for JGit clone is first included in git client plugin 3.0.0-beta1.  Prior to that version, JGit silently ignored timeout settings.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-22400

Jenkins / JENKINS-22400 Git timeout on other actions than fetch/clone

Change By: Mark Waite Status: Reopened Open

Add Comment

[marat@slonopotamus.org (JIRA)]

Marat Radchenko commented on JENKINS-22400

Re: Git timeout on other actions than fetch/clone I'm impressed that you've found a case where it requires more than 10 minutes to complete. Large repo + interrupted checkout during previous build == almost all I/O happens during git reset --hard. If you add LFS to the mix, that I/O also involves transferring files over network. Simpler way to reproduce: just remove everything from working copy, but keep .git it in. Voila, you've got a massive git reset --hard.

Add Comment

[marat@slonopotamus.org (JIRA)]

Marat Radchenko edited a comment on JENKINS-22400

Re: Git timeout on other actions than fetch/clone

bq. I'm impressed that you've found a case where it requires more than 10 minutes to complete. Large repo + interrupted checkout during previous build == almost all I/O happens during {{git reset --hard}}. If you add LFS to the mix, that I/O also involves transferring files over network. Simpler way to reproduce: just remove everything from working copy, but keep {{.git}} it in. Voila, you've got a massive {{git reset --hard}} for next build in the same working copy .

Add Comment

[marat@slonopotamus.org (JIRA)]

Marat Radchenko edited a comment on JENKINS-22400

Re: Git timeout on other actions than fetch/clone

bq. I'm impressed that you've found a case where it requires more than 10 minutes to complete. Large repo + interrupted checkout during previous build == almost all I/O happens during {{git reset --hard}}. If you add LFS to the mix, that I/O also involves transferring files over network.

Simpler way to reproduce: just remove everything from working copy, but keep {{.git}} it in. Voila, you've got a massive {{git reset --hard}} for next build .

Add Comment