[JIRA] (JENKINS-54589) Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

27 kali dilihat
Langsung ke pesan pertama yang belum dibaca

tejas.gr@pwc.com (JIRA)

belum dibaca,
12 Nov 2018, 12.12.0212/11/18
kepadajenkinsc...@googlegroups.com
tejas gr created an issue
 
Jenkins / Bug JENKINS-54589
Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2018-11-12 17:11
Priority: Major Major
Reporter: tejas gr

Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

 
> git.exe config core.sparsecheckout # timeout=10*09:41:33* > git.exe checkout -f ***09:51:33 ERROR: Timeout after 10 minutes*09:51:33* FATAL: Could not checkout ***09:51:33 hudson.plugins.git.GitException: Command "git.exe checkout -f **" returned status code -1:*09:51:33 stdout: 09:51:33 stderr: 09:51:33 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1990)09:51:33 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72)09:51:33 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2289)

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

belum dibaca,
12 Nov 2018, 12.17.0112/11/18
kepadajenkinsc...@googlegroups.com

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

belum dibaca,
12 Nov 2018, 12.20.0312/11/18
kepadajenkinsc...@googlegroups.com

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

belum dibaca,
12 Nov 2018, 12.20.0312/11/18
kepadajenkinsc...@googlegroups.com

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

belum dibaca,
12 Nov 2018, 12.20.0312/11/18
kepadajenkinsc...@googlegroups.com
 

This is not a bug. Please don't use bug reports to request help with configuration issues. Very few people read bug reports for specific plugins, and even fewer respond to requests for help that arrive as bug reports.

Please use the Jenkins chat channels (IRC or gitter) or the Jenkins users mailing list to request help. There are many more users in those locations that can assist.

Change By: Mark Waite
Status: Open Fixed but Unreleased
Assignee: Mark Waite
Resolution: Not A Defect

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 10.52.0213/11/18
kepadajenkinsc...@googlegroups.com
AnneTheAgile reopened an issue
 

This is actually a bug. Perhaps it needs to be clarified. 

I have jobs that are failing git steps within a minute. For example, today, (with variables for the git commit hash and repo):

05:39:46  > git config core.sparsecheckout # timeout=10
05:39:46  > git checkout -f <GITSHA> # timeout=4
05:39:48 Commit message: "Merge pull request #71 from MYORG/MYTICKET-3"
05:39:48  > git rev-list --no-walk <GITSHA> # timeout=10
05:39:48 java.util.concurrent.TimeoutException: Timeout waiting for task.
05:39:48 	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
05:39:48 	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
05:39:48 	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
05:39:48 	at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
05:39:48 	at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)
05:39:48 	at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:135)
05:39:48 	at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:43)
05:39:48 	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120)
05:39:48 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
05:39:48 Caused: java.io.IOException: Failed to parse changelog
05:39:48 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592)
05:39:48 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
05:39:48 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
05:39:48 	at hudson.model.Run.execute(Run.java:1810)
05:39:48 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
05:39:48 	at hudson.model.ResourceController.execute(ResourceController.java:97)
05:39:48 	at hudson.model.Executor.run(Executor.java:429)
05:39:48 [PostBuildScript] - Executing post build scripts.
05:39:48 [ios-DAH] $ /bin/bash -l /var/folders/0r/wr2c4hs13r58l9k7pjdxpnl80000gq/T/jenkins8422288554445462114.sh
 

^^ This only just started after I upgraded jenkins/plugins last night.

 

Change By: AnneTheAgile
Resolution: Not A Defect
Status: Closed Reopened

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 10.53.0313/11/18
kepadajenkinsc...@googlegroups.com
This is actually a bug. Perhaps it needs to be clarified. 

I have jobs that are failing git steps within a minute. For example, today, (with variables for the git commit hash and repo):
{code:java}

05:39:46  > git config core.sparsecheckout # timeout=10
05:39:46  > git checkout -f <GITSHA> # timeout=4
05:39:48 Commit message: "Merge pull request #71 from MYORG/MYTICKET-3"
05:39:48  > git rev-list --no-walk <GITSHA> # timeout=10
05:39:48 java.util.concurrent.TimeoutException: Timeout waiting for task.
05:39:48  at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
05:39:48  at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
05:39:48  at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
05:39:48  at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
05:39:48  at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)
05:39:48  at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:135)
05:39:48  at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:43)
05:39:48  at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120)
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
05:39:48 Caused: java.io.IOException: Failed to parse changelog
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592)
05:39:48  at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
05:39:48  at hudson.model.Run.execute(Run.java:1810)
05:39:48  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
05:39:48  at hudson.model.ResourceController.execute(ResourceController.java:97)
05:39:48  at hudson.model.Executor.run(Executor.java:429)
05:39:48 [PostBuildScript] - Executing post build scripts.
05:39:48 [ios-DAH] $ /bin/bash -l /var/folders/0r/wr2c4hs13r58l9k7pjdxpnl80000gq/T/jenkins8422288554445462114.sh
{code}

^^ This only just started after I upgraded jenkins/plugins last night.

At first I thought the issue was lack of specifically set timeouts so I added git advanced settings for advanced/checkout-options and advanced/clone-options to make timeout 4minutes. That seemed to work, but it did not and is intermittent , as mentioned by OP.  

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.03.0213/11/18
kepadajenkinsc...@googlegroups.com


 

I am on; 

Enterprise Github 2.12.2 (per tooltip on footer/octocat)

Jenkins ver. 2.151
{code:java}
Git plugin  3.9.1
and others such as  Git Changelog  2.11   Git client plugin 2.7.3     Git Pipeline for Blue Ocean  1.8.4    GIT server Plugin  1.7 GitHub API Plugin  1.92   GitHub Branch Source Plugin  2.4.1 {code}
^^ not sure which are the most important , so tried to paste a subset of plugins.

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.05.0113/11/18
kepadajenkinsc...@googlegroups.com
Jenkins ver. 2.151 (after previously was 2.144 and was ok)
{code:java}
Git plugin  3.9.1
and others such as  Git Changelog  2.11   Git client plugin 2.7.3     Git Pipeline for Blue Ocean  1.8.4    GIT server Plugin  1.7 GitHub API Plugin  1.92   GitHub Branch Source Plugin  2.4.1 {code}
^^ not sure which are the most important , so tried to paste a subset of plugins.

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.09.0213/11/18
kepadajenkinsc...@googlegroups.com

tejas gr please let us know what versions you are on, and if you have enterprise github too. 

Also you said restart would fix the issue , do you mean it would be completely failing until you restart? I do not have that, I have intermittent and I have not rebooted to see if that changed it.

Mark Waite I am confused deciding which plugin is the cause of things like this. From this line I decided that regular git might be the cause; 

05:39:48 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 

Am I right?

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.19.0213/11/18
kepadajenkinsc...@googlegroups.com
AnneTheAgile edited a comment on Bug JENKINS-54589
1.

[~tejasgr] please let us know what versions you are on, and if you have enterprise github too. 


Also you said restart would fix the issue , do you mean it would be completely failing until you restart? I do not have that, I have intermittent and I have not rebooted to see if that changed it.

2.

[~markewaite] I am confused deciding which plugin is the cause of things like this. From this line I decided that regular git might be the cause; 
{code:java}
05:39:48  at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) {code}
Am I right?

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.24.0213/11/18
kepadajenkinsc...@googlegroups.com
AnneTheAgile edited a comment on Bug JENKINS-54589
This is actually a bug. Perhaps it It needs to be clarified to show that .  


I have jobs that are failing git steps within a minute. For example, today, (with variables for the git commit hash and repo):
{code:java}
05:39:46  > git config core.sparsecheckout # timeout=10
05:39:46  > git checkout -f <GITSHA> # timeout=4
05:39:48 Commit message: "Merge pull request #71 from MYORG/MYTICKET-3"
05:39:48  > git rev-list --no-walk <GITSHA> # timeout=10
05:39:48 java.util.concurrent.TimeoutException: Timeout waiting for task.
05:39:48  at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
05:39:48  at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
05:39:48  at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
05:39:48  at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
05:39:48  at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)
05:39:48  at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:135)
05:39:48  at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:43)
05:39:48  at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120)
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
05:39:48 Caused: java.io.IOException: Failed to parse changelog
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592)
05:39:48  at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
05:39:48  at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
05:39:48  at hudson.model.Run.execute(Run.java:1810)
05:39:48  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
05:39:48  at hudson.model.ResourceController.execute(ResourceController.java:97)
05:39:48  at hudson.model.Executor.run(Executor.java:429)
05:39:48 [PostBuildScript] - Executing post build scripts.
05:39:48 [ios-DAH] $ /bin/bash -l /var/folders/0r/wr2c4hs13r58l9k7pjdxpnl80000gq/T/jenkins8422288554445462114.sh
{code}
^^ This only just started after I upgraded jenkins/plugins last night.

Another one today,  also taking 1 ms to timeout;
{code:java}
10:03:23  > git rev-list --no-walk <GITSHA> # timeout=10
10:03:24 java.util.concurrent.TimeoutException: Timeout waiting for task.
{code}
 

 

At first I thought the issue was lack of specifically set timeouts so I added git advanced settings for advanced/checkout-options and advanced/clone-options to make timeout 4minutes. That seemed to work, but it did not and is intermittent , as mentioned by OP. 

 

I am on; 

Enterprise Github 2.12.2 (per tooltip on footer/octocat)

Jenkins ver. 2.151 (after previously was 2.144 and was ok)
{code:java}
Git plugin  3.9.1
and others such as  Git Changelog  2.11   Git client plugin 2.7.3     Git Pipeline for Blue Ocean  1.8.4    GIT server Plugin  1.7 GitHub API Plugin  1.92   GitHub Branch Source Plugin  2.4.1 {code}
^^ not sure which are the most important , so tried to paste a subset of plugins.

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 11.25.0213/11/18
kepadajenkinsc...@googlegroups.com

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

belum dibaca,
13 Nov 2018, 11.29.0313/11/18
kepadajenkinsc...@googlegroups.com

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 11.33.0613/11/18
kepadajenkinsc...@googlegroups.com
tejas gr commented on Bug JENKINS-54589
 
Re: Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

Yes. I am also on Enterprise Git 2.15.1. Untill remote server restart where Jenkins installed, the issue will be there. Only with remote server restart where Jenkins installed, the issue will be cleared and again facing it sometime like the next day or back sometime.

 

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

belum dibaca,
13 Nov 2018, 11.36.0313/11/18
kepadajenkinsc...@googlegroups.com

AnneTheAgile the stack trace that you are reporting is dramatically different from the stack trace reported in this bug.

Your stack trace (with my subsetting):

05:39:48 java.util.concurrent.TimeoutException: Timeout waiting for task.
05:39:48 	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
05:39:48 	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
05:39:48 	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
05:39:48 	at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
05:39:48 	at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)
05:39:48 	at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:135)
05:39:48 	at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:43)
05:39:48 	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120)
05:39:48 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)

seems to indicate that Blue Ocean is performing a JQL query to the Jira service to request the list of issues from the Jira service. That query seems to be timing out.

I recommend you either begin a discussion on chat or the mailing list to help identify why your Jira server times out on that request, or open a ticket where those discussions can occur. If you choose to use a ticket, you accept that fewer people will see your request and thus fewer people are likely able to help you.

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

belum dibaca,
13 Nov 2018, 11.38.0113/11/18
kepadajenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Change By: Mark Waite
Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

{noformat}  

> git.exe config core.sparsecheckout # timeout=10*09:41:33*
  
  > git.exe checkout -f ***
*09:51:33* ERROR: Timeout after 10 minutes
*09:51:33* FATAL: Could not checkout ***
*09:51:33* hudson.plugins.git.GitException: Command "git.exe checkout -f ***" returned status code -1:
*09:51:33* stdout:
*09:51:33* stderr:
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1990)
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72)
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2289)
{noformat}

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

belum dibaca,
13 Nov 2018, 11.42.0213/11/18
kepadajenkinsc...@googlegroups.com
 

Reaffirming this is not a bug. The `git checkout` command can have its timeout value adjusted if needed for long checkout (due to a slow file system or a network file system or ...). That's a configuration change, not a bug.

The `git checkout` command is entirely local. It copies content from the local .git repository into the local working directory. It is not performing a network fetch or other network operation of any sort. It is not performing any operations which require credentials (unless you're using git large file support).

Change By: Mark Waite
Status: Reopened Fixed but Unreleased
Resolution: Not A Defect

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

belum dibaca,
13 Nov 2018, 11.43.0213/11/18
kepadajenkinsc...@googlegroups.com

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

belum dibaca,
13 Nov 2018, 11.45.0213/11/18
kepadajenkinsc...@googlegroups.com
Mark Waite updated an issue
Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

{noformat} 
> git.exe config core.sparsecheckout # timeout=10
*09:41:33*  
> git.exe checkout -f ***
*09:51:33* ERROR: Timeout after 10 minutes
*09:51:33* FATAL: Could not checkout ***
*09:51:33* hudson.plugins.git.GitException: Command "git.exe checkout -f ***" returned status code -1:
*09:51:33* stdout:
*09:51:33* stderr:
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1990)
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72)
*09:51:33*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2289)
{noformat}

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 11.46.0213/11/18
kepadajenkinsc...@googlegroups.com
tejas gr commented on Bug JENKINS-54589
 
Re: Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

Hi Mark,

As said its not actually timeout issue as per it says. After the restart, it even checksout within a minute. It always checksout within a minute. When this issue occurs, I did increased the timeout, changed braches and everything and it fails with same error. But once the server restart done, then everything will be fine and any branch checkout will be carried within a minute.

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

belum dibaca,
13 Nov 2018, 11.48.0213/11/18
kepadajenkinsc...@googlegroups.com

tejas gr when you say "remote server restart", do you mean that the GitHub Enterprise server restart seems to be required in order for the `git checkout` command to complete? If not, can you explain further what server is restarted that causes things to be better behaved?

Are you using git large file support in the repository where you're performing that checkout?

Is the Jenkins workspace where the checkout is being performed on some form of network attached storage? If so, is that storage performing reliably?

If on network storage, does the same problem occur if you use local storage instead of network attached storage?

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 11.52.0213/11/18
kepadajenkinsc...@googlegroups.com
tejas gr commented on Bug JENKINS-54589

Hi Mark,

Its not github restart. We have jenkins service installed on a windows server. So when this issue occured, we had to restart this windows server where Jenkins is installed to get it working back again. Yes It is Jenkins workplace to where checkout needs to be performed from github.

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

belum dibaca,
13 Nov 2018, 12.00.0213/11/18
kepadajenkinsc...@googlegroups.com

Is the stack trace in the bug description accurately describing the stack trace that you are seeing when checkout fails to complete on your Windows server? I assume it is. If it is not, then please place an accurate stack trace in the bug report for better diagnosis.

If that stack trace is accurate, then there is a chance that a git process (either from Jenkins or elsewhere) has acquired a lock on the .git} directory inside the Jenkins workspace. That is not something I've ever seen before, but it is conceptually possible that another process might have a lock which causes the local git checkout to block while waiting for the lock to be released.

Next time the problem occurs, use a command prompt window or a git bash Window on the agent where the workspace resides. Attempt to perform git operations (like `git ls-remote origin` and `git status` and `git log`) in that workspace while the Jenkins checkout is blocked.

annemoroney@alum.mit.edu (JIRA)

belum dibaca,
13 Nov 2018, 12.35.0213/11/18
kepadajenkinsc...@googlegroups.com

ty so much  Mark Waite ! I will investigate as you recommend.

FYI I'm using a Mac host for Jenkins server, so I guess many parts of my setup are indeed different from this ticket.

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

belum dibaca,
13 Nov 2018, 14.11.0113/11/18
kepadajenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-54589
Is the stack trace in the bug description accurately describing the stack trace that you are seeing when checkout fails to complete on your Windows server?  I assume it is.  If it is not, then please place an accurate stack trace in the bug report for better diagnosis.

If that stack trace is accurate, then there is a chance that a git process (either from Jenkins or elsewhere) has acquired a lock on the {{.git}}
} directory inside the Jenkins workspace.  That is not something I've ever seen before, but it is conceptually possible that another process might have a lock which causes the local git checkout to block while waiting for the lock to be released.

Next time the problem occurs, use a command prompt window or a git bash Window on the agent where the workspace resides.  Attempt to perform git operations (like `git ls-remote origin` and `git status` and `git log`) in that workspace while the Jenkins checkout is blocked.

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 14.35.0213/11/18
kepadajenkinsc...@googlegroups.com

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 14.35.0213/11/18
kepadajenkinsc...@googlegroups.com
tejas gr commented on Bug JENKINS-54589
 
Re: Builds are failing with timeout during checkout. Issue will be fixed only after the server restart where Jenkins is installed. Intermittent issue but happening frequently. Please assist on this.

It did started the block again. Failing while checkout. I have checked the directory and tried to checkout from git manually from the directory. But got this error. As you said. Yes. It is blocked. But why ut happens? And what would be the resolution for this? Its happening again and again

tejas.gr@pwc.com (JIRA)

belum dibaca,
13 Nov 2018, 14.45.0213/11/18
kepadajenkinsc...@googlegroups.com
Balas ke semua
Balas ke penulis
Teruskan
0 pesan baru