BitBucket is a common provider used by those seeking private repository support with great integration into existing Atlassian products (like Jira and Confluence).
Below is the complete set of options that can be used to configure your integration.
oauth should be provided.
Otherwise, you will only have access to public repositories.
I’ve found that
basic using an application password has been the easiest to configure.
accounts: # full bitbucket schema - bitbucket: users: - "<username>" teams: - "<teamname>" strategy: "SSH | HTTP" basic: username: "<username>" password: "<app_password>" oauth: token: "<oauth_token>" application_id: "<application_id>"
Due to the variance in each of the client, there are a few oddities between each of the implementations. While we work on getting parity between each of the providers take note that this implementation:
- does not pull groups for the authenticated user
- does not pull groups for the configured users
- pulls repositories for all configured users and groups
Crawl all of Atlassian’s public repositories on BitBucket.
accounts: - bitbucket: teams: - atlassian strategy: HTTP
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.