{"action":"created","issue":{"url":"https://api.github.com/repos/drone/drone/issues/1243","labels_url":"https://api.github.com/repos/drone/drone/issues/1243/labels{/name}","comments_url":"https://api.github.com/repos/drone/drone/issues/1243/comments","events_url":"https://api.github.com/repos/drone/drone/issues/1243/events","html_url":"https://github.com/drone/drone/issues/1243","id":112244090,"number":1243,"title":"Git clone hangs when using depth","user":{"login":"brgaulin","id":4007825,"avatar_url":"https://avatars.githubusercontent.com/u/4007825?v=3","gravatar_id":"","url":"https://api.github.com/users/brgaulin","html_url":"https://github.com/brgaulin","followers_url":"https://api.github.com/users/brgaulin/followers","following_url":"https://api.github.com/users/brgaulin/following{/other_user}","gists_url":"https://api.github.com/users/brgaulin/gists{/gist_id}","starred_url":"https://api.github.com/users/brgaulin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brgaulin/subscriptions","organizations_url":"https://api.github.com/users/brgaulin/orgs","repos_url":"https://api.github.com/users/brgaulin/repos","events_url":"https://api.github.com/users/brgaulin/events{/privacy}","received_events_url":"https://api.github.com/users/brgaulin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-19T22:14:01Z","updated_at":"2015-10-19T22:36:11Z","closed_at":null,"body":"Not sure what is happening but I decided to give a go with the new 0.4.0 branch and I can't clone my repo =(\r\n\r\nThis is the console output\r\n```\r\n[info] Pulling image plugins/drone-git:latest\r\n$ git init\r\nInitialized empty Git repository in /drone/src/github.company.com/bgaulin/app/.git/\r\n$ git remote add origin https://github.company.com/bgaulin/app.git\r\n$ git fetch --no-tags --depth=50 origin +refs/heads/development:\r\n```\r\n\r\nWhen I do a docker exec with that fetch command and verbose it just hangs. But when I remove the --depth argument, it seems to go just fine.\r\n\r\nSo I guess the easier request would be to remove the --depth as being necessary. But I was wondering first if anyone else had this issue and worked through it.\r\n\r\nThis is using github enterprise. \r\n\r\nThe verbose output just has this one line\r\n```\r\nPOST git-upload-pack (143 bytes)\r\n```\r\n\r\nKind of solved:\r\n\r\nTo get around this for now I specified tags: true. That cancels the shallow clone which apparently does it.. so maybe nevermind this issue.\r\n\r\nFigured I would still submit this in case someone else hits this issue"},"comment":{"url":"https://api.github.com/repos/drone/drone/issues/comments/149367049","html_url":"https://github.com/drone/drone/issues/1243#issuecomment-149367049","issue_url":"https://api.github.com/repos/drone/drone/issues/1243","id":149367049,"user":{"login":"bradrydzewski","id":817538,"avatar_url":"https://avatars.githubusercontent.com/u/817538?v=3","gravatar_id":"","url":"https://api.github.com/users/bradrydzewski","html_url":"https://github.com/bradrydzewski","followers_url":"https://api.github.com/users/bradrydzewski/followers","following_url":"https://api.github.com/users/bradrydzewski/following{/other_user}","gists_url":"https://api.github.com/users/bradrydzewski/gists{/gist_id}","starred_url":"https://api.github.com/users/bradrydzewski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bradrydzewski/subscriptions","organizations_url":"https://api.github.com/users/bradrydzewski/orgs","repos_url":"https://api.github.com/users/bradrydzewski/repos","events_url":"https://api.github.com/users/bradrydzewski/events{/privacy}","received_events_url":"https://api.github.com/users/bradrydzewski/received_events","type":"User","site_admin":false},"created_at":"2015-10-19T22:36:11Z","updated_at":"2015-10-19T22:36:11Z","body":"In 0.4 we switched from `git+ssh` to `git+https`. The company that also experienced this issue was running a version of GitHub Entperprise from Dec 2014 (which they said was end of life last month). They are in the process of upgrading and found this was no longer an issue in the newer version of GitHub Enterprise (v2.1).\r\n\r\nIn the meantime, until they are fully migrated, we added a special parameter called `ssh=true` that will override and use `git+ssh` instead of `git+http`. You can set this parameter in your remote configuration string.\r\n\r\nLet me know if you have any luck there"}}