[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Vincenzo Melandri commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I am seeing a similar problem, but with ubuntu agents. It works with freestyle, but on declarative pipeline it doesn't work. It does not even try to load the reference repo for me. 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.195401.154214014.3792.1569285540210%40Atlassian.JIRA.
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Timor Raiman commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I'm seeing this with the pipeline only. (freestyle works). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195401.154214014.229.1558020180128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title dheeraj reddy updated an issue Jenkins / JENKINS-54612 Reference repo not used for Git clones on Windows SSH agents Change By: dheeraj reddy Priority: Minor Critical 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-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title dheeraj reddy commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I am also facing the exact issue(same environment also) while using git plugin (either as pipeline code or freestyle job). Using cmd or sh script I am able to clone it utilizing reference repo. May I know is there any bug on the git plugin ?? 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-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title
Adam Brousseau updated an issue
Jenkins / JENKINS-54612
Reference repo not used for Git clones on Windows SSH agents
Change By:
Adam Brousseau
We use a reference repo on all our agents to speed up our clones. This seems to work on all agents we have except for our Windows nodes. I first noticed that the fetch times were slower on the Windows nodes. I then confirmed by checking the size of the .git folder on each machine after the clone. All non-windows nodes were 11MB whereas the .git folder on Windows was 1.9GB.Our Windows agents are connected over ssh (Cygwin). The Remote Root is on C:\ (windows style path) and the reference repository is also on C:\. We use the Checkout/SCM pipeline step in order to take advantage of extra options not available using the Git step.This is a simplified snippet of what we use I pulled from the Syntax generator.{code:none}checkout([ $class: 'GitSCM', branches: [[name: '$BRANCH']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: false, reference: '$REFERENCE_REPO', shallow: false]], gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[url: '$REPO']]]){code}The console output tries to convince me it's using the reference repo but it appears it isn't (3:20 to fetch).{code:none}00:41:39.279 Cloning the remote Git repository00:41:39.355 Cloning repository https://github.com/***/***.git00:41:39.368 > git init C:\Users\jenkins\workspace\Build # timeout=1000:41:39.574 Using reference repository: C:\repo_cache00:41:39.574 Fetching upstream changes from https://github.com/***/***.git00:41:39.574 > git --version # timeout=1000:41:39.606 > git fetch --tags --progress https://github.com/***/***.git +refs/heads/*:refs/remotes/origin/* # timeout=3000:45:00.369 > git config remote.origin.url https://github.com/***/***.git # timeout=1000:45:00.431 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=1000:45:00.603 > git config remote.origin.url https://github.com/***/***.git # timeout=1000:45:00.775 Fetching upstream changes from https://github.com/***/***.git00:45:00.776 > git fetch --tags --progress https://github.com/***/***.git +refs/heads/*:refs/remotes/origin/* # timeout=3000:45:02.416 > git rev-parse "origin/master^{commit}" # timeout=1000:45:02.448 Checking out Revision *** (origin/master)00:45:02.588 > git config core.sparsecheckout # timeout=1000:45:02.619 > git checkout -f *** # timeout=3000:46:45.479 Commit message: "Merge pull request #63 from ***/***"{code}I've tried various things like using Windows Git to populate the reference repo, using a Jenkins git step to populate the repo, using cygwin style paths for both the ref repo location and/or the remote root dir for the agent. Not sure what else I can try but I assume its going to be something related to windows vs cygwin vs path styles vs line-endings. Edit: I can use an sh step to clone using the ref repo successfully.
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54612 Reference repo not used for Git clones on Windows SSH agents Change By: Mark Waite Assignee: Mark Waite 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-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Adam Brousseau created an issue Jenkins / JENKINS-54612 Reference repo not used for Git clones on Windows SSH agents Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-11-13 20:15 Environment: Jenkins 2.138.2 Git Plugin 3.9.1 Windows 2012r2 Cygwin Git 2.17.0 Labels: windows git Priority: Minor Reporter: Adam Brousseau We use a reference repo on all our agents to speed up our clones. This seems to work on all agents we have except for our Windows nodes. I first noticed that the fetch times were slower on the Windows nodes. I then confirmed by checking the size of the .git folder on each machine after the clone. All non-windows nodes were 11MB whereas the .git folder on Windows was 1.9GB. Our Windows agents are connected over ssh (Cygwin). The Remote Root is on C:\ (windows style path) and the reference repository is also on C:\. We use the Checkout/SCM pipeline step in order to take advantage of extra options not available using the Git step. This is a simplified snippet of what we use I pulled from the Syntax generator. checkout([ $class: 'GitSCM', branches: [[name: '$BRANCH']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: false, reference: '$REFERENCE_REPO', shallow: false]], gitTool: 'Default', submoduleCfg: [],
