subject:"\[JIRA\] \[git\-client\] \(JENKINS\-20387\) Timeout \(10min\) on git clone command"















































Josh Santangelo
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Still seeing this with git plugin 2.2.1, git client plugin 1.9.1 and Jenkins 1.567.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Josh Santangelo
 reopened  JENKINS-20387


Timeout (10min) on git clone command
















Still seeing this with git plugin 2.2.1, git client plugin 1.9.1 and Jenkins 1.567.





Change By:


Josh Santangelo
(10/Jun/14 10:17 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

2014-06-10 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Does one of the submodules which is being updated by the "submodule update --init --recursive" require authentication?  

Is that authentication different than the parent repository?

My theory is that the "git submodule update" is blocking with an authentication prompt.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Josh Santangelo
 commented on  JENKINS-20387


Timeout (10min) on git clone command















They are both private github repositories which require authentication, but I have many jobs with such repositories and there are no authentication prompts since the SSL certificates are configured correctly.

Even if it was blocking on an auth prompt, I would expect it to time out after the 240 minutes specified in the configuration rather than the default of 10.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

2014-06-10 Thread mark.earl.wa...@gmail.com (JIRA)

Mark Waite
commented on JENKINS-20387

Timeout (10min) on git clone command

There are two different classes of timeout in the plugin. Timeout for fetch is governed by the setting in the UI. Timeout for operations which are not fetch are fixed at 10 minutes, at least in one or more cases I've detected. Since fetch is the primary network operation which may be slow, non non-fetch operations are almost entirely local operations, the timeout setting has been a reasonable heuristic.

Is there any way you can test my theory that the "git submodule" command is blocking on an authentication prompt? For example, can you see if your git server is sending lots of data to the client while that command is blocked? If the server is sending lots of data, then it is not an authentication prompt which is blocking.

Are the submodule repositories expected to take a long time to clone (because they are large)?

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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

Josh Santangelo
commented on JENKINS-20387

Timeout (10min) on git clone command

My workaround for this issue has been to do the initial clone and submodule update from a command shell on the server. This works great and doesn't prompt for any authentication because it's using certificates. The submodule ("Cinder") is rather large and has several submodules within it. Cloning it definitely takes longer than ten minutes, so the timeout isn't entirely surprising. (It is a fork of this: https://github.com/cinder/Cinder/tree/dev)

So, I don't think it's blocking on an authentication prompt, both because it works fine from the command line, and also because the parent repo and the submodule both have the same authentication, and the parent works fine. Also when either the parent or submodule are updated, Jenkins gets those updates reliably. It's just the initial clone that's a problem.

If there's another way I can confirm, let me know, and thanks for your help.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

2014-06-10 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-20387


Timeout (10min) on git clone command















I think that description is enough to recommend that the "git submodule update" command needs to be wrapped in the same timeout as the "git fetch" commands.

Thanks for the report.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

2014-06-02 Thread j...@stimulant.io (JIRA)















































Josh Santangelo
 commented on  JENKINS-20387


Timeout (10min) on git clone command















I'm still seeing this issue using the latest version of Jenkins and all Git plugins. Below I have added the contents of the job's config.xml and the console output of the build. I am seeing this problem in both matrix builds and "freestyle" ones too. This is Jenkins running on Windows as a service.

config.xml
?xml version='1.0' encoding='UTF-8'?
project
  actions/
  description/description
  keepDependenciesfalse/keepDependencies
  properties/
  scm class="hudson.plugins.git.GitSCM" plugin="git@2.2.1"
configVersion2/configVersion
userRemoteConfigs
  hudson.plugins.git.UserRemoteConfig
urlg...@github.com:stimulant/IMR4.git/url
  /hudson.plugins.git.UserRemoteConfig
/userRemoteConfigs
branches
  hudson.plugins.git.BranchSpec
name*/dev/name
  /hudson.plugins.git.BranchSpec
/branches
doGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurations
submoduleCfg class="list"/
extensions
  hudson.plugins.git.extensions.impl.CloneOption
shallowfalse/shallow
reference/reference
timeout240/timeout
  /hudson.plugins.git.extensions.impl.CloneOption
  hudson.plugins.git.extensions.impl.SubmoduleOption
disableSubmodulesfalse/disableSubmodules
recursiveSubmodulestrue/recursiveSubmodules
trackingSubmodulesfalse/trackingSubmodules
  /hudson.plugins.git.extensions.impl.SubmoduleOption
/extensions
  /scm
  canRoamtrue/canRoam
  disabledfalse/disabled
  blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding
  blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding
  triggers
hudson.triggers.SCMTrigger
  specH/5 * * * */spec
  ignorePostCommitHooksfalse/ignorePostCommitHooks
/hudson.triggers.SCMTrigger
  /triggers
  concurrentBuildfalse/concurrentBuild
  builders/
  publishers/
  buildWrappers/
/project


console
Building in workspace C:\Jenkins\jobs\git-test\workspace
Cloning the remote Git repository
Cloning repository g...@github.com:stimulant/IMR4.git
  C:\Program Files (x86)\Git\cmd\git.exe init C:\Jenkins\jobs\git-test\workspace
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
  C:\Program Files (x86)\Git\cmd\git.exe --version
  C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/*:refs/remotes/origin/*
  C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git
  C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
  C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
  C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/*:refs/remotes/origin/*
  C:\Program Files (x86)\Git\cmd\git.exe rev-parse "origin/dev^{commit}"
Checking out Revision dec485282d92247c404fe5a76c4dcfd75ace7b00 (origin/dev)
  C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout
  C:\Program Files (x86)\Git\cmd\git.exe checkout -f dec485282d92247c404fe5a76c4dcfd75ace7b00
First time build. Skipping changelog.
  C:\Program Files (x86)\Git\cmd\git.exe remote
  C:\Program Files (x86)\Git\cmd\git.exe submodule init
  C:\Program Files (x86)\Git\cmd\git.exe submodule sync
  C:\Program Files (x86)\Git\cmd\git.exe config --get remote.origin.url
  C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive
ERROR: Timeout after 10 minutes
FATAL: Command "C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive" returned status code -1:
stdout: 
stderr: Cloning into 'Cinder'...

hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive" returned status code -1:
stdout: 
stderr: Cloning into 'Cinder'...

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1325)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:87)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:733)
	at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:77)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:909)
	at

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

2014-05-16 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Paulo Matos Since I could not reproduce JENKINS-22547 and cannot reproduce this report this report either, I need more information.  Could you upload your job definition configuration file (job-name/config.xml)?  Maybe I can find some insights in your job definition file.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Paulo Matos
 commented on  JENKINS-20387


Timeout (10min) on git clone command















The new timeout option does not work for matrix projects, so you might still get the same error for matrix projects. What else can be done?



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

Mark Waite
commented on JENKINS-20387

Timeout (10min) on git clone command

Could you describe the situation where timeout settings are ignored in matrix projects? I assume you mean a job which Jenkins calls a "multi-configuration project".

I defined a multi-configuration project, set the timeout to 1 minute, and attempted to clone a 6 GB repository to Windows 6.1, Windows 6.2, Debian 7.5, and Debian Testing. The flyweight repository (created on initial job start) correctly honored the timeout and stopped the clone operation after 1 minute.

I then modified the job definition to use a reference repository and to create the initial flyweight repository on the master server so that it could use that reference repository for a faster clone. The flyweight repository was cloned successfully and the jobs started on the other machines. The two Windows machines failed their clone in 1 minute because they don't have a copy of the reference repository. As far as I can tell, the timeout option is honored by multi-configuration projects the same as it is honored for other projects.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command

Paulo Matos
commented on JENKINS-20387

Timeout (10min) on git clone command

Correct, I have a multi-configuration project with 1 axis and 4 different rows.
For each I am cloning GCC (which is a huge git repo) on a machine which has about 200 other jenkins jobs running, so by default these clones (or even just fetches) take a long time.

Running Jenkins ver. 1.532.2 with git plugin 2.0.4.
I have setup a job with a 60 minutes timeout. However, sometimes I still get mails with:

Started by upstream project "fptools_gcc-25x_test" build number 584 originally caused by:
Started by upstream project "fptools_gcc-25x" build number 659 originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building on master in workspace http://jenkins-cam-04.cam.broadcom.com/job/fptools_gcc-25x_test/archs=fp4014/ws/
Fetching changes from the remote Git repository Fetching upstream changes from dsl-...@eng-cbga-2.cam.broadcom.com:tools/fp_gcc
Checking out Revision 4c981a3cc80a89868d6c5185865537c90ffd7af7 (origin/FP_GCC_2_5_X_BRANCH)
ERROR: Timeout after 10 minutes
FATAL: Could not checkout null with start point 4c981a3cc80a89868d6c5185865537c90ffd7af7
hudson.plugins.git.GitException: Could not checkout null with start point 4c981a3cc80a89868d6c5185865537c90ffd7af7
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkou...
...

Note that the logs say: ERROR: Timeout after 10 minutes
The job fptools_gcc-25x_test was set with a timeout of 60 minutes therefore the job http://jenkins-cam-04.cam.broadcom.com/job/fptools_gcc-25x_test/archs=fp4014 should have inherited it.
I am happy to provide further information to help diagnose the problem.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Mark Waite
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Your git plugin version is out of date.  That probably also means your git client plugin is out of date.  The most recent git plugin is 2.2.1.  The most recent git client plugin is 1.9.0.

Since you're working with a large repository and many jobs, you probably should consider placing a bare repository in a well known location, like /var/lib/git/gcc.git, then include the path to that reference repository in the job definition near the location where you assigned the timeout value.  That will reduce your disc use, dramatically reduce the clone time, and will reduce the CPU load on your git server.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Mark Waite
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Are you using submodules in your job configuration?  If so, then you definitely need a newer version of the git plugin and the git client plugin, since timeout was not being copied to submodule updates.  Submodules (unfortunately) do not have an easy way to use reference repositories.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Paulo Matos
 commented on  JENKINS-20387


Timeout (10min) on git clone command















And, no we are not using submodules. Thanks.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command















































Paulo Matos
 commented on  JENKINS-20387


Timeout (10min) on git clone command















Thanks for the tips. We have just recently started used Jenkins so we are still trying to understand all the in/outs of the system.



























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/d/optout.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command