[JIRA] (JENKINS-59380) Jenkins fetch is too slow

7 views
Skip to first unread message

barakvalzer@gmail.com (JIRA)

unread,
Sep 15, 2019, 12:04:03 PM9/15/19
to jenkinsc...@googlegroups.com
barak valzer created an issue
 
Jenkins / Bug JENKINS-59380
Jenkins fetch is too slow
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2019-09-15 16:03
Environment: Jenkins 2.194, Gitea 1.9.3, Git client 2.23 and git plugin 3.12.1
Labels: jenkins git windows configuration
Priority: Blocker Blocker
Reporter: barak valzer

I'm configuring a Jenkins environment for my company.

when i build a repository from source code management it builds the repository but it takes between 120-150 seconds to do a fetch command.
any suggestions on what to do?

I tried to change git clients, make sure the credentials are ok, tried with empty or full repository and with sub modules and only one branch configuration.

the problematic part:

 C:\Program Files\Git\cmd\git.exe fetch --no-tags --force --progress https://XXX:3000/Tests/test-repo.git +refs/heads/:refs/remotes/origin/**

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

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

unread,
Sep 15, 2019, 12:25:02 PM9/15/19
to jenkinsc...@googlegroups.com
Mark Waite updated Bug JENKINS-59380
 

Please don't use the bug tracker to request assistance. When you use the bug tracker to request help, you are relying on the very small group of people that watch the bug tracker to answer your question instead of the much, much larger group of people that monitor the Jenkins user mailing list and the Jenkins chat channels on IRC and gitter. That reduces the chance of you receiving an answer and reduces the time that maintainers can spend maintaining and enhancing Jenkins and its plugins.

Please as questions in the Jenkins user mailing list rather than asking them in the bug tracker.

For the specific question, "How do I improve the performance of git clones?", refer to the Jenkins World 2017 "Git in the Large" video or to the slides from the Jenkins World 2019 talk "Git for Jenkins - faster and better"

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

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

unread,
Sep 15, 2019, 12:26:02 PM9/15/19
to jenkinsc...@googlegroups.com
Please don't use the bug tracker to request assistance.  When you use the bug tracker to request help, you are relying on the very small group of people that watch the bug tracker to answer your question instead of the much, much larger group of people that monitor the Jenkins user mailing list and the Jenkins chat channels on IRC and gitter.  That reduces the chance of you receiving an answer and reduces the time that maintainers can spend maintaining and enhancing Jenkins and its plugins.

Please as ask questions in the Jenkins user mailing list rather than asking them in the bug tracker.

For the specific question, "How do I improve the performance of git clones?", refer to the Jenkins World 2017  "[Git in the Large|https://youtu.be/jBGFjFc6Jf8?t=6434]" video or to the slides from the Jenkins World 2019 talk "[Git for Jenkins - faster and better|https://www.slideshare.net/markewaite/git-for-jenkins-faster-and-better]"

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

unread,
Sep 15, 2019, 12:26:03 PM9/15/19
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Fixed but Unreleased Closed
Reply all
Reply to author
Forward
0 new messages