-
Notifications
You must be signed in to change notification settings - Fork 0
Changelog: Bitbucket Integration Setup #72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| --- | ||
| title: "Bitbucket" | ||
| description: "Configure repository access for Bitbucket and self-hosted Bitbucket." | ||
| --- | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| The Bitbucket account used to connect Hacktron must: | ||
|
|
||
| - Have access to the repository you want Hacktron to review. | ||
| - Have Admin permission on each selected repository so Hacktron can create and update repository webhooks. | ||
| - Be able to sign in to Bitbucket and approve the OAuth Request. | ||
|
|
||
| <Info> | ||
| We recommend using a dedicated Bitbucket account for the Hacktron integration instead of an employee's personal account. This keeps repository access and automated pull request comments associated with a separate integration identity.<br /><br />A dedicated account is **optional**; an existing Bitbucket repository administrator can also connect to Hacktron | ||
| </Info> | ||
|
|
||
| <Warning> | ||
| Bitbucket Cloud does not provide native service or bot accounts. A "dedicated Bitbucket account" means a normal, login-capable Bitbucket user created for the integration. | ||
| </Warning> | ||
|
|
||
| ## Configure access | ||
|
|
||
| <Steps> | ||
| <Step title="Create a dedicated Bitbucket account (recommended)"> | ||
| You can skip this step if you intend to connect Hacktron using an existing Bitbucket repository administration. | ||
| </Step> | ||
| <Step title="Grant repository access"> | ||
| In Bitbucket, open **Repository settings** → **Repository permissions** and select **Add users or groups**. | ||
|
|
||
| Add the account that will connect Hacktron, assign the **Admin** permission, and click **Confirm**. | ||
|
|
||
| <Note> | ||
| For multiple repositories, you can manage access through a Bitbucket group or grant the account **Admin** permission at the project level. | ||
| </Note> | ||
|
|
||
|  | ||
| </Step> | ||
| <Step title="Sign in to Bitbucket"> | ||
| Sign in with the dedicated Bitbucket account you created in step 1. If you chose to use an existing repository administrator account, sign in with that account instead. | ||
| </Step> | ||
| <Step title="Open the Integrations page "> | ||
| In Hacktron, go to **Integrations** and click **Connect** under **Bitbucket** | ||
|
|
||
|  | ||
| </Step> | ||
| <Step title="Authorise Hacktron"> | ||
| Review the permissions requested by Hacktron and click **Accept.** | ||
|
|
||
| Bitbucket will redirect you to Hacktron after authorization is complete. | ||
|
|
||
| <img | ||
| src="/Bitbucket-Integration-Authorisation.png" | ||
| alt="GitLab Integration" | ||
| lightAlt="Bitbucket integration authorisation" | ||
| darkAlt="Bitbucket integration authorisation" | ||
| className="dark:hidden" | ||
| /> | ||
| <img | ||
| src="Bitbucket-Integration-Authorisation.png" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When a reader uses dark mode, this relative URL resolves beneath the current documentation route (for example, Useful? React with 👍 / 👎. |
||
| alt="GitLab Integration" | ||
| lightAlt="Bitbucket integration authorisation" | ||
| darkAlt="Bitbucket integration authorisation" | ||
| className="hidden dark:block" | ||
| /> | ||
| </Step> | ||
| <Step title="Select repositories"> | ||
| Select the repositories you want Hacktron to review and save your selection. | ||
|
|
||
| Hacktron automatically creates the required webhook for each enabled repository. You do not need to configure the webhook manually. | ||
|
|
||
|  | ||
|
|
||
| To verify the webhook, open the repository in Bitbucket and go to **Repository settings** → **Webhooks**. You should see an active webhook named **Hacktron Security Scan** pointing to: `https://iva.hacktron.ai/api/v1/webhooks/bitbucket` | ||
|
|
||
|  | ||
| </Step> | ||
| </Steps> | ||
|
|
||
| That's it! Hacktron will now run security reviews for every pull request in the selected repositories. | ||
|
|
||
| ## Supported Bitbucket deployments | ||
|
|
||
| Hacktron currently supports Bitbucket Cloud. | ||
|
|
||
| Bitbucket Data Center and other self-hosted Bitbucket deployments are not currently supported. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The page description advertises configuration for self-hosted Bitbucket, but the support section explicitly states that Bitbucket Data Center and other self-hosted deployments are not supported. This contradictory metadata can send self-hosted customers to instructions that cannot work; limit the description to Bitbucket Cloud.
Useful? React with 👍 / 👎.