[JIRA] (JENKINS-14575) SCM checkout retry count not working

2020-01-13 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-14575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-14575  
 
 
  SCM checkout retry count not working   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.145260.1343246886000.7716.1578962882498%40Atlassian.JIRA.


[JIRA] (JENKINS-14575) SCM checkout retry count not working

2019-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan edited a comment on  JENKINS-14575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM checkout retry count not working   
 

  
 
 
 
 

 
 Same issue here. Here's my code snippet: {code:none}stage('checkout') {steps {retry(env.TRY_COUNT) {timeout(time: 45, unit: 'SECONDS') {checkout scm}}}}{code}Environment:- Linux- Jenkins 2.150.1- Pipeline plugin 2.5- Pipeline: Declarative plugin 1.3.2- git repository- Git plugin 3.9.1- Git Client plugin 2.7.3- Git Pipeline for Blue Ocean plugin 1.5.4 What happens is:- when the {{checkout scm}} fails due to a time-out, it just falls through the {{retry}}- in other words: the _retry_ is not even attempted  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-14575) SCM checkout retry count not working

2019-02-16 Thread er...@ernstdehaan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan commented on  JENKINS-14575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM checkout retry count not working   
 

  
 
 
 
 

 
 Same issue here. Here's my code snippet:  

 

stage('checkout') {
steps {
retry(env.TRY_COUNT) {
timeout(time: 45, unit: 'SECONDS') {
checkout scm
}
}
}
}
 

 Environment: 
 
Linux 
Jenkins 2.150.1 
Pipeline plugin 2.5 
Pipeline: Declarative plugin 1.3.2 
git repository 
Git plugin 3.9.1 
Git Client plugin 2.7.3 
Git Pipeline for Blue Ocean plugin 1.5.4 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-14575) SCM checkout retry count not working

2019-01-10 Thread jenk...@sofiedc.be (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sofie De Cooman commented on  JENKINS-14575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM checkout retry count not working   
 

  
 
 
 
 

 
 We still run into this issue - we're using git plugin v3.8.0 e.g. while loading a shared pipeline library on a multibranch-pipeline We got error "unable to access [shared pipeline repo git repo url]: The requested URL returned error: 504 WorkflowScript: Loading libraries failed   No retry is done to load the shared pipeline library, while SCM retry count is set to 5   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-14575) SCM checkout retry count not working

2018-09-15 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-14575  
 
 
  SCM checkout retry count not working   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-30 Thread w...@wooh.hu (JIRA)














































Adam PAPAI
 commented on  JENKINS-14575


SCM checkout retry count not working















This solves the issue:

https://github.com/jenkinsci/git-plugin/pull/143

We're waiting for the merge.



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-28 Thread w...@wooh.hu (JIRA)














































Adam PAPAI
 commented on  JENKINS-14575


SCM checkout retry count not working















I've just fixing this. I got the bug.



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-28 Thread w...@wooh.hu (JIRA)















































Adam PAPAI
 assigned  JENKINS-14575 to Adam PAPAI



SCM checkout retry count not working
















Change By:


Adam PAPAI
(28/Mar/13 9:07 AM)




Assignee:


AdamPAPAI



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-28 Thread w...@wooh.hu (JIRA)














































Adam PAPAI
 started work on  JENKINS-14575


SCM checkout retry count not working
















Change By:


Adam PAPAI
(28/Mar/13 9:22 AM)




Status:


Open
InProgress



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-13 Thread nicolas.del...@gmail.com (JIRA)














































Nicolas De Loof
 commented on  JENKINS-14575


SCM checkout retry count not working















git plugin 1.3.0 uses JGit to fetch (in combination with git-client 1.0.4), can you give it a try ?



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-13 Thread mo...@egis-software.com (JIRA)














































Moshe Immerman
 commented on  JENKINS-14575


SCM checkout retry count not working















I tried git plugin and this seems to have made things worse:

I now get this exception when cloning on a windows 2003 machine:

FATAL: Invalid path: installation/full/service.vmoptions 
org.eclipse.jgit.dircache.InvalidPathException: Invalid path: installation/full/service.vmoptions 
	at org.eclipse.jgit.dircache.DirCacheCheckout.processEntry(DirCacheCheckout.java:526)
	at org.eclipse.jgit.dircache.DirCacheCheckout.preScanTwoTrees(DirCacheCheckout.java:248)
	at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:405)
	at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391)
	at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:240)
	at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64)
	at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1261)
	at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57)
	at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1220)
	at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:287)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:60)
	at java.lang.Thread.run(Unknown Source)


On a windows 2008 server the clone process stalls after:

Using strategy: Default
Fetching changes from 1 remote Git repository


Ubuntu based servers in the same multi configuration build are cloning fine.



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-03-04 Thread mo...@egis-software.com (JIRA)














































Moshe Immerman
 commented on  JENKINS-14575


SCM checkout retry count not working















I am prepared to sponsor this: http://www.freedomsponsors.org/core/offer/214/scm-checkout-retry-count-not-working



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-02-14 Thread markewa...@java.net (JIRA)














































markewaite
 updated  JENKINS-14575


SCM checkout retry count not working
















Change By:


markewaite
(15/Feb/13 3:04 AM)




Component/s:


multiple-scms



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2013-02-07 Thread jonathan.cla...@normation.com (JIRA)














































Jonathan Clarke
 commented on  JENKINS-14575


SCM checkout retry count not working















I'm also seeing this with Jenkins ver. 1.480.1 on Debian.

This is the error I get:


08:46:36 Cloning the remote Git repository
08:46:36 Cloning repository ssh://g...@git.normation.com/repo.git
08:46:36 git --version
08:46:36 git version 1.7.2.5
08:46:57 ERROR: Error cloning remote repo 'origin' : Could not clone ssh://g...@git.normation.com/repo.git
08:46:57 hudson.plugins.git.GitException: Could not clone ssh://g...@git.normation.com/repo.git
08:46:57 	at hudson.plugins.git.GitAPI.clone(GitAPI.java:273)
08:46:57 	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
08:46:57 	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
08:46:57 	at hudson.FilePath.act(FilePath.java:842)
08:46:57 	at hudson.FilePath.act(FilePath.java:824)
08:46:57 	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986)
08:46:57 	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142)
08:46:57 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
08:46:57 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
08:46:57 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
08:46:57 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
08:46:57 	at hudson.model.Run.execute(Run.java:1502)
08:46:57 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
08:46:57 	at hudson.model.ResourceController.execute(ResourceController.java:88)
08:46:57 	at hudson.model.Executor.run(Executor.java:236)
08:46:57 Caused by: hudson.plugins.git.GitException: Command "git clone --progress -o origin ssh://g...@git.normation.com/repo.git /var/lib/jenkins/jobs/rudder-server-packages-2.5-branch-RPM-SLES11/workspace" returned status code 128:
08:46:57 stdout: Cloning into /var/lib/jenkins/jobs/rudder-server-packages-2.5-branch-RPM-SLES11/workspace...
08:46:57 
08:46:57 stderr: ssh: connect to host git.normation.com port 22: Connection timed out
08:46:57 fatal: The remote end hung up unexpectedly
08:46:57 
08:46:57 	at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897)
08:46:57 	at hudson.plugins.git.GitAPI.access$000(GitAPI.java:42)
08:46:57 	at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:269)
08:46:57 	at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:248)
08:46:57 	at hudson.FilePath.act(FilePath.java:842)
08:46:57 	at hudson.FilePath.act(FilePath.java:824)
08:46:57 	at hudson.plugins.git.GitAPI.clone(GitAPI.java:248)
08:46:57 	... 14 more
08:46:57 Trying next repository
08:46:57 ERROR: Could not clone repository
08:46:57 FATAL: Could not clone
08:46:57 hudson.plugins.git.GitException: Could not clone
08:46:57 	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1056)
08:46:57 	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
08:46:57 	at hudson.FilePath.act(FilePath.java:842)
08:46:57 	at hudson.FilePath.act(FilePath.java:824)
08:46:57 	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986)
08:46:57 	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142)
08:46:57 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
08:46:57 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
08:46:57 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
08:46:57 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
08:46:57 	at hudson.model.Run.execute(Run.java:1502)
08:46:57 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
08:46:57 	at hudson.model.ResourceController.execute(ResourceController.java:88)
08:46:57 	at hudson.model.Executor.run(Executor.java:236)



























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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14575) SCM checkout retry count not working

2012-08-09 Thread lka...@gmail.com (JIRA)














































Łukasz Nowak
 updated  JENKINS-14575


SCM checkout retry count not working
















Change By:


Łukasz Nowak
(09/Aug/12 7:33 PM)




Component/s:


git





Component/s:


plugin



























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






[JIRA] (JENKINS-14575) SCM checkout retry count not working

2012-07-25 Thread lka...@gmail.com (JIRA)














































Łukasz Nowak
 created  JENKINS-14575


SCM checkout retry count not working















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


plugin



Created:


25/Jul/12 8:08 PM



Description:


From time to time I reveive error when getting SCM changes from Git repository and the option "SCM checkout retry count" (I have set it to 3) is not working. 

ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
hudson.plugins.git.GitException: Command "git fetch -t g...@github.com:xxx/xxx +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout: 
stderr: ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly

	at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:818)
	at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:780)
	at hudson.plugins.git.GitAPI.fetch(GitAPI.java:196)
	at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1026)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:812)
	at hudson.plugins.git.GitSCM.access$100(GitSCM.java:90)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1096)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064)
	at hudson.FilePath.act(FilePath.java:842)
	at hudson.FilePath.act(FilePath.java:824)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1249)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
	at hudson.model.Run.execute(Run.java:1488)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
ERROR: Could not fetch from any repository
FATAL: Could not fetch from any repository
hudson.plugins.git.GitException: Could not fetch from any repository
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1103)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064)
	at hudson.FilePath.act(FilePath.java:842)
	at hudson.FilePath.act(FilePath.java:824)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1249)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
	at hudson.model.Run.execute(Run.java:1488)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)




Environment:


Jenkins 1.473 on Debian




Project:


Jenkins



Priority:


Blocker



Reporter:


Łukasz Nowak

























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