SEI Bitbucket enterprise integration
Bitbucket is a web-based version control repository hosting service, for source code and development projects that use either Mercurial or Git revision control systems.
Use the SEI Bitbucket integration to integrate SEI with Bitbucket Cloud or Bitbucket Enterprise.
Requirements
The following permissions and settings are required to use the SEI Bitbucket integration:
- You have a Bitbucket account.
- Your role is Member or higher.
Configure the integration
- Private On-Prem
- Public On-Prem
- In your Harness Project, select the SEI Module, and go to your Account.
- Select Integrations under Settings.
- Select Available Integrations, and locate the Bitbucket Enterprise integration, and select Install
- Select Install.
- Configure and Save the integration.
- Provide a Name for the integration.
- The Description and Tags are optional.
- Enter the URL for the Bitbucket Private Instance in the format
https://bitbucket.org/<TEAMNAME_OR_USERNAME>/<REPOSITORY_NAME>/src
- Enter your Username
- Enter the Bitbucket API Key. To generate an API key for your Bitbucket instance, go to Managing API tokens for Bitbucket.
- Enter Tags and the List of repositories you want to ingest. You can leave this option blank if you want to ingest all the repositories from organizations accessible to the token user.
- You can select the Filters to define the type of data you want to ingest. The available options are Fetch Commits, Fetch PRs, Fetch PRs Reviews, Fetch Commits Fields.
- Download the
satellite.yml
file and update it following the instructions here.
If you experience any issues while configuring the integration using the Ingestion Satellite, refer to the Ingestion Satellite Troubleshooting and FAQs.
Here’s a sample satellite.yaml
:
satellite:
tenant: <ACCOUNT_ID>
api_key: <ACCOUNT_API_KEY>
url: 'https://app.harness.io/gratis/sei/api' # Note that this URL is relative to the Environment of your Harness Account.
integrations:
- id: '<INTEGRATION_ID>'
application: bitbucket_server
url: 'https://bitbucket.org/<TEAMNAME_or_USERNAME>/<REPO_NAME>/src'
username: <BITBUCKET_USERNAME>
api_key: <BITBUCKET_API_KEY>
metadata:
fetch_prs: true
fetch_pr_reviews: true
fetch_commits: true
fetch_commit_files: true
repos: <REPOSITORIES>
satellite: true
The steps for configuring the public on-premises integration for Bitbucket is similar to the private on-premises integration, with the exception of using satellite to communicate with the Bitbucket server. Instead, the public on-premises integration directly uses the credentials provided by the user to authenticate with the Bitbucket server.