Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails during second lfs fetch in Checkout job if the repository uses Git LFS - Log shows Git credential and password errors #2272

edgariscoding opened this issue May 24, 2019 · 1 comment


None yet
2 participants
Copy link

commented May 24, 2019

Having issue with Tasks?

During the Checkout job of the build process, the agent checks the Git version ( and the Git LFS version (2.7.1). Based on some research I've done, it seems like version 2.7.1 of Git LFS may be causing this issue. Version 2.7.2 was released a few days ago to address this but my agent still has 2.7.1 and I'm not sure how to update this specific package. Running the build on a repository with the same codebase that does not use LFS works perfectly fine, it's only when LFS is used that I receive these errors. The errors also seem to be related to credential/password issues... so if there's something else you can suggest to fix this, I'd be glad to try.

See the GitHub issues below for details:

Agent Version and Platform

Version of your agent? 2.150.3

OS of the machine running the agent? Windows

Azure DevOps Type and Version
If, what is your organization name?

What's not working?

Here are some of the relevant lines from the Checkout Job log:

##[command]git version
git version
##[command]git lfs version
git-lfs/2.7.1 (GitHub; windows amd64; go 1.11.5; git 6b7fb6e3)
##[command]git init "D:\a\1\s"
Initialized empty Git repository in D:/a/1/s/.git/
##[command]git remote add origin
##[command]git config 0
##[command]git config --get-all http.
##[command]git config --get-all http.proxy
##[command]git lfs install --local
Updated git hooks.
Git LFS initialized.
##[command]git -c http.extraheader="AUTHORIZATION: bearer ***" fetch --tags --prune --progress --no-recurse-submodules origin
remote: Azure Repos        
remote: Found 565657 objects to send. (1283 ms)        
Receiving objects:   0% (1/565657)   
Receiving objects:   1% (5657/565657) 
Receiving objects: 100% (565657/565657), 2.11 GiB | 24.13 MiB/s, done.
Resolving deltas:   0% (0/436110)   
Resolving deltas:   1% (4362/436110)   
Resolving deltas: 100% (436110/436110), done.
##[command]git -c http."AUTHORIZATION: bearer ***" lfs fetch origin 4cbe37*
fetch: Fetching reference 4cbe37*
fatal: could not read Password for '': terminal prompts disabled
batch response: Git credentials for not found.
error: failed to fetch some objects from ''
##[warning]Git lfs fetch failed with exit code 2, back off 5.844 seconds before retry.
##[command]git lfs logs last
No logs to show
##[error]Git lfs fetch failed with exit code: 2. Git lfs logs returned with exit code: 0.

This comment has been minimized.

Copy link

commented Jun 6, 2019

Hi @edgariscoding,

A new Windows image containing version 2.7.2 of git lfs will be deployed, expected to begin this week. The Checkout Job should eventually start working once the new image gets deployed to CiraConnect.

See this comment for more details about the deployment schedule: microsoft/azure-pipelines-image-generation#800 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.