[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small
Josh Santangelo commented on JENKINS-20445 Git plugin timeout is too small I have the Git plugin 2.0.3, and Git Client Plugin 1.6.3, but I don't see any new option. Am I just missing it? 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite closed JENKINS-20445 as Fixed Git plugin timeout is too small Change By: Mark Waite (25/Feb/14 8:13 PM) Status: Resolved Closed 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small In the job configuration page under the Git plugin section, there is a drop-down list "Add". Within that dropdown list there is a selection "Advanced clone behaviours". When you add the advanced clone behaviors, you'll see a field for "Timeout (in minutes) for clone and fetch operation". 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] [git] (JENKINS-20445) Git plugin timeout is too small
Christian Höltje commented on JENKINS-20445 Git plugin timeout is too small Is there a way we can bump up the priority for releasing 2.0.3 with the fix? This broke our LTS systems using the stable plugins channel. We have windows systems that do git clones very very slowly. When we rolled back to 1.5.0 we lose build history because the build.xml files can't load. I assume there was an incompatible XML change between 1.5.0 and 2.0.0? I'll attach an example traceback. 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] [git] (JENKINS-20445) Git plugin timeout is too small
Christian Höltje updated JENKINS-20445 Git plugin timeout is too small This is a traceback of what happens if we try to rollback to 1.5 after having been on 2.0.1. Our log file is full of these and bunches of jobs missing build histories. And we were having things retriggering over and over again as if they didn't know about previous builds. Change By: Christian Höltje (14/Feb/14 3:59 PM) Attachment: traceback.out 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small The git-plugin 2.0 release was a major change (as noted by the change of major number in the version string). It changes the job definition and simplifies the user interface dramatically. There is no facility for "downgrade", or rollback on major version changes like that. It is already challenging enough assuring that old versions upgrade correctly. If you need the plugin sooner, it may be simplest for you to build it yourself to confirm that it works for your use case. I've built a copy of the git-plugin based on https://github.com/jenkinsci/git-plugin/commit/eec487fc52ca3165fc8190858cea23e3e3a21db0 . It is not an official release, but you could download it and try it at https://www.dropbox.com/s/tsoboofl14ejwrj/git.hpi 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite edited a comment on JENKINS-20445 Git plugin timeout is too small Pull request has been accepted. This fix is available in git-client-plugin 1.6.2. It will also need the next release of the git-plugin after 2.0.2 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite edited a comment on JENKINS-20445 Git plugin timeout is too small Pull requests have been accepted to both git-client-plugin and git-plugin. This fix is available in git-client-plugin 1.6.2. It will also need the next release of the git-plugin after 2.0.2 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite resolved JENKINS-20445 as Fixed Git plugin timeout is too small Pull request has been accepted. This fix should be available in the next release of the git-client-plugin after 1.6.1 Change By: Mark Waite (04/Feb/14 12:03 PM) Status: Open Resolved Resolution: Fixed 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small Pull request has been submitted to git-client-plugin https://github.com/jenkinsci/git-client-plugin/pull/92 and to git-plugin https://github.com/jenkinsci/git-plugin/pull/197 proposing to include timeout setting in the Git plugin user interface. 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] [git] (JENKINS-20445) Git plugin timeout is too small
Eric Borts commented on JENKINS-20445 Git plugin timeout is too small Note this also timed out on my home 28 Mbps connection without the Jetpack. Though it looks like the Jenkins service is being throttled to 700 KiB/s (~5.4 Mbps). Is there any way to change the timeout? Or do I need to find a workaround and/or revert to an older version of the 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 -- 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] [git] (JENKINS-20445) Git plugin timeout is too small
Eric Borts
edited a comment on JENKINS-20445
Git plugin timeout is too small
Same problem here. I'm currently working over a Verizon Jetpack (for numerous reasons). The Jetpack fails when 2 computers try to SSH simultaneously, and in this case 10 minutes is too long. When I use only a single computer, the Jetpack works fine, and the 10 minute timeout is too short. The repository gets to about 25% before aborting. It would be great if the plugin could detect that the `git clone` process is doing valid work, and not abort. This was mentioned as point #1 of the original issue ("what if git is doing actual work?").
Admittedly, some of what I'm battling could be the 4GLTE/Jetpack issues. But this really seems like a timeout issue. Here is my output:
Fetching upstream changes from g...@github.com:user/Example.git
ERROR: Timeout after 10 minutes
FATAL: Failed to fetch from g...@github.com:user/Example.git
hudson.plugins.git.GitException: Failed to fetch from g...@github.com:user/Example.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
at hudson.model.Run.execute(Run.java:1678)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress g...@github.com:user/Example.git +refs/heads/*:refs/remotes/origin1/*" returned status code 128:
stdout:
stderr: warning: no common commits
remote: Reusing existing pack: 14500, done. [K
Receiving objects: 0% (1/14500)
Receiving objects: 1% (145/14500)
Receiving objects: 2% (290/14500)
Receiving objects: 3% (435/14500)
Receiving objects: 3% (555/14500), 508.00 KiB | 487.00 KiB/s
Receiving objects: 3% (555/14500), 1.11 MiB | 550.00 KiB/s
...snipped...
Receiving objects: 23% (3357/14500), 339.12 MiB | 608.00 KiB/s
Receiving objects: 23% (3358/14500), 339.75 MiB | 613.00 KiB/s
Receiving objects: 23% (3358/14500), 340.37 MiB | 610.00 KiB/s
Receiving objects: 23% (3358/14500), 341.00 MiB | 606.00 KiB/s
fatal: early EOF
fatal: The remote end hung up unexpectedly
fatal: index-pack failed
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224)
at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610)
... 10 more
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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small Refer to JENKINS-20387 for instructions on how to set the timeout. I think this report is a duplicate of JENKINS-20387. 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] [git] (JENKINS-20445) Git plugin timeout is too small
Eric Borts commented on JENKINS-20445 Git plugin timeout is too small Thanks Mark. This definitely seems like a duplicate of 20387. Your pointers over there were very helpful. 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small If you have only 12 kb/second throughput from Jenkins to your git repository, you should probably consider cloning a bare copy of the repository to central location on the Jenkins server, then perform the clone with the "Advanced clone behaviour" to use a reference repository. That will significantly reduce the amount of data transferred from the git server to Jenkins. On my Debian Jenkins machine, I do that with: $ sudo mkdir -p /var/cache/git/mwaite $ sudo chown mwaite.mwaite /var/cache/git/mwaite $ cd /var/cache/git/mwaite $ git clone --bare https://github.com/jenkinsci/jenkins.git After that bare clone is available on the Jenkins machine, add that advanced behavior to the job and it should perform much better. 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] [git] (JENKINS-20445) Git plugin timeout is too small
Mark Waite edited a comment on JENKINS-20445 Git plugin timeout is too small If you have only 30 kb/second throughput from Jenkins to your git repository, you should probably consider cloning a bare copy of the repository to central location on the Jenkins server, then perform the clone with the "Advanced clone behaviour" to use a reference repository. That will significantly reduce the amount of data transferred from the git server to Jenkins. On my Debian Jenkins machine, I do that with: $ sudo mkdir -p /var/cache/git/mwaite $ sudo chown mwaite.mwaite /var/cache/git/mwaite $ cd /var/cache/git/mwaite $ git clone --bare https://github.com/jenkinsci/jenkins.git After that bare clone is available on the Jenkins machine, add that advanced behavior to the job and it should perform much better. 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.
