[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo Vincenzo Melandri that seems like a separate bug report is needed. Pipeline has some overhead compared to Freestyle but that much overhead is beyond what I expected. 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.202115.1569286759000.4491.1569362100112%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Vincenzo Melandri commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo I made a brand new job that just checkouts the repo and cats a file to isolate it from interference and I found out that it works, but there is still a massive difference: A test freestyle jobs checks out the repo in under 5 seconds, while the job defined with pipeline takes upward of 40s, which is still faster than a non-referenced checkout, which takes about 400 seconds.. 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.202115.1569286759000.4428.1569351720157%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo The RelativeTargetDir extension is not recommended for use in Pipeline. The dir() and ws() directives are native Pipeline directives that are better suited for use than the git plugin specific extension RelativeTargetDir. That does not affect this case, but is good advice for your implementation. My test cases used both dir() and RelativeTargetDir successfully. 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.202115.1569286759000.3836.1569299460303%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite updated JENKINS-59497 Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo Change By: Mark Waite Status: Fixed but Unreleased Closed 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.202115.1569286759000.3841.1569299460375%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite updated JENKINS-59497 Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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.202115.1569286759000.3831.1569299340302%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo I can't duplicate the problem you're describing. I've created a test job that confirms the reference repository is honored by both command line git and JGit. I've confirmed that for the command line git implementation, the diagnostic message is consistently printed and the reference repository is consistently used. The reference repository path may be specified incorrectly in the checkout step. The reference repository may be missing on the agent where the workspace is being created. 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.202115.1569286759000.3829.1569299340272%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo Change By: Mark Waite Assignee: Mark Waite 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.202115.1569286759000.3818.1569298200181%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title
Vincenzo Melandri created an issue
Jenkins / JENKINS-59497
Git clone in pipeline ignoring reference repo
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-09-24 00:59
Environment:
Jenkins 2.176.1 Git Plugin 3.9.1
Labels:
pipeline git
Priority:
Major
Reporter:
Vincenzo Melandri
On a freestyle project, everything works fine, but on a declarative pipeline I cannot make the reference repository to work Example of how we check out in the pipeline:
checkout(
[
$class : 'GitSCM',
branches : [[ name: "${branch}" ]],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class : 'RelativeTargetDirectory',
relativeTargetDir: targetDir
],
[$class : 'CloneOption',
reference: '/somefolder/repo'
]
],
userRemoteConfigs : [[
url : ssh://blahblah/some.git,
credentialsId: ourCredentialsId
]]
]
)
and the output looks like this:
[Pipeline] git
Fetching changes from the remote Git
