[JIRA] (JENKINS-57710) Git checkout fails when using "Git LFS pull after checkout"

27 views
Skip to first unread message

nt@3yourmind.com (JIRA)

unread,
May 28, 2019, 6:49:02 AM5/28/19
to jenkinsc...@googlegroups.com
Nando Theessen created an issue
 
Jenkins / Bug JENKINS-57710
Git checkout fails when using "Git LFS pull after checkout"
Issue Type: Bug Bug
Assignee: Unassigned
Components: bitbucket-branch-source-plugin
Created: 2019-05-28 10:48
Environment: bitbucket-branch-source-plugin 2.4.4
Jenkins 2.164.3
Priority: Major Major
Reporter: Nando Theessen

Hi!
We have a BB repository with git-lfs enabled. Whenever we chose to "git-lfs pull after checkout" (which we need in order for this build to succeed) we get the following error:

 
 

Cloning the remote Git repository   Cloning with configured refspecs honoured and without tags   Cloning repository https://bitbucket.org/3yourmind/meshrepair.git 
 

 > git init /home/jenkins/agent/workspace/EV-635-jenkins-ci-implementation # timeout=10 
 

Fetching upstream changes from https://bitbucket.org/3yourmind/meshrepair.git   > git --version # timeout=10  using GIT_ASKPASS to set credentials   > git fetch --no-tags --force --progress https://bitbucket.org/3yourmind/meshrepair.git +refs/heads/DEV-635-jenkins-ci-implementation:refs/remotes/origin/DEV-635-jenkins-ci-implementation  Fetching without tags  Checking out Revision 9bf80e426b1df16381f859979cc36364ae4fbfdd (DEV-635-jenkins-ci-implementation)  Enabling Git LFS pull   > git config remote.origin.url https://bitbucket.org/3yourmind/meshrepair.git # timeout=10 
 

 > git config --add remote.origin.fetch +refs/heads/DEV-635-jenkins-ci-implementation:refs/remotes/origin/DEV-635-jenkins-ci-implementation # timeout=10   > git config remote.origin.url https://bitbucket.org/3yourmind/meshrepair.git # timeout=10 
 

Fetching upstream changes from https://bitbucket.org/3yourmind/meshrepair.git   using GIT_ASKPASS to set credentials 
 

 > git fetch --no-tags --force --progress https://bitbucket.org/3yourmind/meshrepair.git +refs/heads/DEV-635-jenkins-ci-implementation:refs/remotes/origin/DEV-635-jenkins-ci-implementation 
 

 > git config core.sparsecheckout # timeout=10 
 

 > git checkout -f 9bf80e426b1df16381f859979cc36364ae4fbfdd 
 

 > git branch -a -v --no-abbrev # timeout=10 
> git checkout -b DEV-635-jenkins-ci-implementation 9bf80e426b1df16381f859979cc36364ae4fbfdd

Could not checkout DEV-635-jenkins-ci-implementation with start point 9bf80e426b1df16381f859979cc36364ae4fbfdd

 
 
It was working at a stage before this started happening, but now simply does not. It checks out normally when running without the Git LFS pull option. 
There were no force pushes and I've tried to just use a new branch and implement my changes there with no avail.
Other workarounds I have found have not worked either.
 
Any input on this would be appreciated.
 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.earl.waite@gmail.com (JIRA)

unread,
Sep 25, 2019, 3:03:06 PM9/25/19
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Fixed but Unreleased Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Sep 25, 2019, 3:03:53 PM9/25/19
to jenkinsc...@googlegroups.com
 

Please don't use bug reports as a way to ask for help. In this case, the bug report was assigned to the wrong plugin, so was not seen until now. It should have been assigned to the git plugin and the question and related discussion should be in the Jenkins users mailing list or in one of the chat channels.

Change By: Mark Waite
Status: Open Fixed but Unreleased
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages