-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
bitbucket-branch-source-plugin 2.4.4
Jenkins 2.164.3
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.