# Bitbucket Checkout SSH Key **URL:** \ **Category:** Deployments\ **Tags:** bitbucket\ **Created:** [November 27, 2018, 3:25pm UTC](https://discuss.circleci.com/t/bitbucket-checkout-ssh-key/26753 "2018-11-27T15:25:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![loffelmacher](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/loffelmacher/32/10161_2.png) [@loffelmacher](https://discuss.circleci.com/u/loffelmacher)\ **Post date:** [November 27, 2018, 3:25pm UTC](https://discuss.circleci.com/t/bitbucket-checkout-ssh-key/26753/1 "2018-11-27T15:25:57Z")
I’ll look over the entire list of 42 bitbucket-tagged posts to try and find more info, but I cannot seem to pull in a second repository to my build from Bitbucket. Not with Bash, not with the UI, I guess I should start to look at the API. Is there some documentation anywhere about this? Closest I’ve found [is this](https://circleci.com/docs/2.0/gh-bb-integration/#enable-your-project-to-check-out-additional-private-repositories) but it’s not helping. The other weird thing is that I go into the Circle Project setting, make a “Checkout SSH Key” and it shows up in the Circle UI with a little bitbucket logo, which would make you think that it worked, but now my build won’t even clone the main repo down. So broken for bitbucket. _Update_: got this working with the [directions I found here](https://discuss.circleci.com/t/checkout-fails-with-user-key-bitbucket/8735/7?u=loffelmacher) but this is like duct tape, I question the durability of this kind of setup. ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [February 25, 2019, 3:34pm UTC](https://discuss.circleci.com/t/bitbucket-checkout-ssh-key/26753/2 "2019-02-25T15:34:15Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.