Details

    • Similar Issues:

      Description

      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/**

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment - - edited

          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 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" video or to the slides from the Jenkins World 2019 talk "Git for Jenkins - faster and better"

          Show
          markewaite Mark Waite added a comment - - edited 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 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 " video or to the slides from the Jenkins World 2019 talk " Git for Jenkins - faster and better "

            People

            • Assignee:
              markewaite Mark Waite
              Reporter:
              barakvalzer barak valzer
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: