[JIRA] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Ankit Maroo commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use HI, I am also getting stuck with this issue. Hope to see resolution soon. Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title
Scott Richmond edited a comment on JENKINS-30318
Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use
Hey guys. So. The reason this is an issue is because Git LFS uses various Git hooks to run its binary download processes. There hooks don't fire if one uses the granular Git commands that make up a {{git clone}} or {{git pull}} etc. Its not really a bug, its just Git design.If it really is a difficulty in using {{git clone}}, that is fine. The other option in this case is to simply explicitly support Git LFS by adding an option in the settings of this plugin such as {{Enable/Use Git LFS}} and to run {{git lfs pull}} when appropriate.Feel free to drop into the ( Gitter chat room ) ( [https://gitter.im/github/git-lfs] ) for Git LFS, where we have a fairly active community including the key maintainers of the project.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title
Scott Richmond edited a comment on JENKINS-30318
Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use
Hey guys. So. The reason this is an issue is because Git LFS uses various Git hooks to run its binary download processes. There hooks don't fire if one uses the granular Git commands that make up a {{git clone}} or {{git pull}} etc. Its not really a bug, its just Git design.If it really is a difficulty in using {{git clone}}, that is fine. The other option in this case is to simply explicitly support Git LFS by adding an option in the settings of this plugin such as {{Enable/Use Git LFS}} and to run {{git lfs pull}} when appropriate. Feel free to drop into the (Gitter chat room)[https://gitter.im/github/git-lfs] for Git LFS, where we have a fairly active community including the key maintainers of the project.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title
Scott Richmond edited a comment on JENKINS-30318
Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use
Hey guys. So. The reason this is an issue is because Git LFS uses various Git hooks to run its binary download processes. There hooks don't fire if one uses the granular Git commands that make up a ` {{ git clone ` }} or ` {{ git pull ` }} etc. Its not really a bug, its just Git design.If it really is a difficulty in using ` {{ git clone ` }} , that is fine. The other option in this case is to simply explicitly support Git LFS by adding an option in the settings of this plugin such as ' {{ Enable/Use Git LFS ' }} and to run ` {{ git lfs pull ` }} when appropriate.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Scott Richmond commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use Hey guys. So. The reason this is an issue is because Git LFS uses various Git hooks to run its binary download processes. There hooks don't fire if one uses the granular Git commands that make up a `git clone` or `git pull` etc. Its not really a bug, its just Git design. If it really is a difficulty in using `git clone`, that is fine. The other option in this case is to simply explicitly support Git LFS by adding an option in the settings of this plugin such as 'Enable/Use Git LFS' and to run `git lfs pull` when appropriate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Alex Agranov commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use I haven't tracked down the exact code that limits to clone/pull but their own man-page refers to their supported functionality: https://github.com/github/git-lfs/blob/master/docs/man/git-lfs-install.1.ronn#L27-L30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-30318 Git plugin breaks usage of Git LFS due to lack of Git Clone use Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Nicolas De Loof commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use I'm +1 to use git clone if we have a correct workaround for credentials support. That being said, I don't get why git-lfs would not support init + fetch. Is there any special hook during a clone operation that git-lfs rely on to get large file downloaded ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Jacob Keller commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use We can fix Git plugin, but there is an issue. The init+fetch workaround would allow us to avoid an issue with checking out into a non-empty directory (which currently we do a "wipe" of the workspace which breaks multiple-SCM plugin if the order of repositories is bad). However, I would propose going ahead with this fix, assuming the maintainer agrees. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title alex karpinski commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use I can reproduce the same state Alex Agranov mentioned. But I really don't want to manually initialize a workspace any time I'm working with an LFS repo. I'd really prefer to have an appropriate way to work with LFS in Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Alex Agranov commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use Can we raise the priority of this issue? It is currently not possible to add jobs with Git repos making use of git-lfs strictly via Jenkins UI. At best, the current workaround I've found is the following: Via Jenkins Credentials, add a "Username with Password" credential Create new job, making sure to use HTTPS url for repo and not GIT, along with credentials from previous step Attempt first build, it will fail on git-lfs. Make note of `git checkout -f ` that failed. Manually ssh into Jenkins box, cd to job workspace, and re-attempt `git checkout -f `. When prompted, enter U/P Subsequent builds for this job will run unattended Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Jacob Keller commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use The original reasoning for this hack was due to credentials issues, which should be resolved after the 1.20.0-beta3 release, if I understand correctly. However, the decision to remove the init+fetch was not accepted at the time I suggested it. The reasoning for init+fetch was due to needing abillity to use the git credential store inside .git/config which does not exist when you perform a clone. This can be fixed using the GIT_SSH and GIT_ASKPASS programs as I did for fixing submodule credentials issues among other related problems. I would promote removal of the git init+fetch combination due to this, as the original reason for this workaround should no longer be valid. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Scott Richmond updated an issue Jenkins / JENKINS-30318 Git plugin breaks usage of Git LFS due to lack of Git Clone use Change By: Scott Richmond Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Scott Richmond created an issue Jenkins / JENKINS-30318 Git plugin breaks usage of Git LFS due to lack of Git Clone use Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin, git-plugin Created: 05/Sep/15 4:33 PM Priority: Major Reporter: Scott Richmond I'm currently involved in setting up a Jenkins-based build for our project and I've found that the popular Git plugin for Jenkins takes the slightly weird approach of git init+fetch instead of git clone when setting up the repo on agent machines. This appears to break Git LFS as all the binary files are still only the reference pointer files. The plugin does not currently appear to have any advanced options to force git cloning and there are a number of aged active tickets for the plugin to support it. I have raised an issue ticket over at Git LFS to discuss options with regards to this problem, which can be viewed here. It is not an issue for them to resolve, however they may be helpful in providing advice on how to best solve the problem for the plugin that provides minimal impact.
