Unable to clone Bitbucket repository on Databricks Legacy

[lawal-hash]

For the past 3 weeks, I have been unable to clone the Bitbucket repository into Databricks legacy.
I got the following error message 
"Error Creating Repo
There was an error performing the operation. Please try again or open a support ticket.
"
I would appreciate it if anybody could assist me on how to solve this error.

[Kaniz_Fatma]

Hi @lawal-hash, I understand that you’ve encountered issues while trying to clone a Bitbucket repository into Databricks legacy. 

The error message you received, “Error Creating Repo. There was an error operating. Please try again or open a support ticket,” can be frustrating. 

Let’s explore some potential solutions to address this problem:

Check Git Credentials:

• Ensure that your Git credentials are correctly configured in your Databricks User Settings. Navigate to User Settings -> Git Integration and verify that your personal access token or app passw....

Clone Depth:

• When cloning from Bitbucket, consider adjusting the “Clone depth” setting. In Sourcetree, under “Advanced Options,” set the “Clone depth” to 1 instead of 0. If the repository clone works with this setting, you can run the following command in the terminal: ....

Proxy Settings:

• If you’re using a proxy, configure the proxy settings for your Git CLI. You can set the proxy configuration using the following command: git config --global http.proxy https://user...
• If necessary, you can also disable SSL verification with the following command:git config --global http.sslverify false
• However, please use caution when disabling SSL verification.

Connection Issues:

• The error message “fatal: the remote end hung up unexpectedly” indicates that Bitbucket unexpectedly closed the connection without providing further details. This could be due to network issues or other factors.

Open a Support Ticket:

• If none of the above solutions resolve the issue, consider opening a support ticket with Databricks. They can provide more specific assistance based on your environment and configuration.

Remember to document any changes you make during troubleshooting, and feel free to reach out if you need further assistance. 🛠️