{"action":"closed","issue":{"url":"https://api.github.com/repos/github/git-lfs/issues/1246","repository_url":"https://api.github.com/repos/github/git-lfs","labels_url":"https://api.github.com/repos/github/git-lfs/issues/1246/labels{/name}","comments_url":"https://api.github.com/repos/github/git-lfs/issues/1246/comments","events_url":"https://api.github.com/repos/github/git-lfs/issues/1246/events","html_url":"https://github.com/github/git-lfs/issues/1246","id":156572930,"number":1246,"title":"LFS and TeamCity agent check out","user":{"login":"mjwitte32","id":6289038,"avatar_url":"https://avatars.githubusercontent.com/u/6289038?v=3","gravatar_id":"","url":"https://api.github.com/users/mjwitte32","html_url":"https://github.com/mjwitte32","followers_url":"https://api.github.com/users/mjwitte32/followers","following_url":"https://api.github.com/users/mjwitte32/following{/other_user}","gists_url":"https://api.github.com/users/mjwitte32/gists{/gist_id}","starred_url":"https://api.github.com/users/mjwitte32/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjwitte32/subscriptions","organizations_url":"https://api.github.com/users/mjwitte32/orgs","repos_url":"https://api.github.com/users/mjwitte32/repos","events_url":"https://api.github.com/users/mjwitte32/events{/privacy}","received_events_url":"https://api.github.com/users/mjwitte32/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-05-24T18:08:11Z","updated_at":"2016-05-25T15:04:40Z","closed_at":"2016-05-25T15:04:40Z","body":"I'm having a bear of a time trying to get my team's TeamCity agents to check out files tracked with LFS. We're using SSH for fetching from the remote. Just from reading other issues, I know SSH isn't the best supported by LFS, but we don't have any other option. Our repo is so damn large that the checkout times out when using HTTPS, so we're stuck with SSH. We use SSH keys to authenticate with the remote, which is hosted on Bitbucket Server.\r\n\r\nEvery build I've run fails when trying to download the first LFS-tracked file with exit status 255. I'm fairly certain this is an authentication issue. I've run the `ssh git@remote.com git-lfs-authenticate org/repo.git download` command (with my own remote, org, and repo, of course), but instead of getting JSON like everyone else, I'm met with a password prompt for git@remote.com. We didn't use a password when setting up the SSH key, but an empty password isn't accepted. Using the build user's domain password isn't accepted either. I tried adding the build user's credentials into `git credentials`, but that didn't help at all.\r\n\r\nI've been wrestling with this now for two days, so if there's any help you can offer, I would be very appreciative. I don't know if it's something I'm doing wrong or if LFS isn't going to support this configuration. I'm sure it's the former, but I don't want to continue banging my head against a wall if it really is impossible."}}
{"actor":{"display_login":"mjwitte32"}}