[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-58049  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
 This is not a bug as far as I can tell.  Refer to [my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-58049/Jenkinsfile] for a working example.I was able to confirm that sparse checkout is not correctly supported by the command line git version that is included with CentOS 6.  CentOS 6 includes command line 1.7.1 which is not supported by the Jenkins git plugin.  There are authentication modes which that old version of command line git does not support and several other features which are not available.  The current version of command line git is 2.22.0. Sparse checkout is also not supported by the JGit implementation that is bundled inside the git client plugin.  However, the JGit implementation is not enabled by default.  If it is enabled and a Pipeline job is configured to use it, and the Pipeline job attempts to perform a sparse checkout, then the Pipeline checkout will fail with a message that sparse checkout is not supported by JGit.  
 

  
 
 
 
 

 
 
 

 
 
 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.200070.1560780449000.1913.1560797880117%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-58049  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58049  
 
 
  GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.200070.1560780449000.1911.1560796800233%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-58049  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
 This is not a bug as far as I can tell.  Refer to [my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-58049/Jenkinsfile] for a working example. I was able to confirm that sparse checkout is not correctly supported by the command line git version that is included with CentOS 6.  CentOS 6 includes command line 1.7.1 which is not supported by the Jenkins git plugin.  There are authentication modes which that old version of command line git does not support and several other features which are not available.  The current version of command line git is 2.22.0.  
 

  
 
 
 
 

 
 
 

 
 
 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.200070.1560780449000.1909.1560796800198%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58049  
 
 
  GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200070.1560780449000.1872.1560790740284%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-58049  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is not a bug as far as I can tell. Refer to my jenkins-bugs repo for a working example.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58049  
 
 
  GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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.200070.1560780449000.1870.1560790680203%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58049  
 
 
  GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 Hi,While trying to use sparseCheckout option under jenkins build step or in pipeline script. i am unable to use it for multiple directories checkout. In both instances the path mentioned at the last checks out ignoring the earlier ones. This is the code i am using  {noformat} checkout( [ $class: 'GitSCM',  branches: [[name: '*/master']],  doGenerateSubmoduleConfigurations: false, extensions: [ [$class: 'SparseCheckoutPaths', sparseCheckoutPaths: [[path: 'TIA-Profiles/*'], [path: '${TARGET_ENVIRONMENT}/*']]] ],  submoduleCfg: [],  userRemoteConfigs: [ [ credentialsId: '***', url: 'ssh://g...@bitbucket.internal.fbd.ie:7999/rem/properties.git' ]]]) {noformat}  It ignores the first path  [path: 'TIA-Profiles/*'] and only checks-out path: '${TARGET_ENVIRONMENT}/*']Out Repo contitutes of multiple directories and properties files and we don't want to checkout all of it in workspace due security and space constraints. Had tried multiple different ways of doing it but does not works. Kindly suggest.Thanks,    
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones

2019-06-17 Thread goda...@fbd.ie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Khushboo Godara created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58049  
 
 
  GIT SparseCheckout for multiple clones   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-06-17 14:07  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Khushboo Godara  
 

  
 
 
 
 

 
 Hi, While trying to use sparseCheckout option under jenkins build step or in pipeline script. i am unable to use it for multiple directories checkout. In both instances the path mentioned at the last checks out ignoring the earlier ones.  This is the code i am using  checkout( [ $class: 'GitSCM',  branches: [[name: '*/master']],  doGenerateSubmoduleConfigurations: false, extensions: [ [$class: 'SparseCheckoutPaths', sparseCheckoutPaths: [[path: 'TIA-Profiles/*'], [path: '${TARGET_ENVIRONMENT}/*']]] ],  submoduleCfg: [],  userRemoteConfigs: [ [ credentialsId: '***', url: 'ssh://g...@bitbucket.internal.fbd.ie:7999/rem/properties.git' ]]])   It ignores the first path  [path: 'TIA-Profiles/*'] and only checks-out path: '${TARGET_ENVIRONMENT}/*'] Out Repo contitutes of multiple directories and properties files and we don't want to checkout all of it in workspace due security and space constraints. Had tried multiple different ways of doing it but does not works.  Kindly suggest. Thanks,