Connect Bitbucket
BetaSee every Bitbucket pull request and deploy on Delivery, and show Flamio Scout results on their commits.
Connect a Bitbucket Cloud workspace and Delivery shows every pull request and Bitbucket Pipelines deploy of the repositories you pick — checked or not, with its author, the branch it merges into and when it merged. With Show Scout results in Bitbucket on, each Scout check your pipeline runs, and each staging check, also shows on its commit and pull request in Bitbucket.
Before you begin
- You need the Editor, Admin or Owner role.
- Signing in and allowing Flamio happen on bitbucket.org, with a Bitbucket account that can read the repositories.
- Updates are instant when you are an admin of the workspace, or of the repository. Any other repository is read every 10 minutes.
- Deploys come from Bitbucket Pipelines deployments. A Scout result reaches a commit for checks your pipeline runs with a CI key — see Check every deployed preview from CI — and for staging checks.
What Flamio reads and writes
- Reads: your workspaces and whether you are an admin of each, the repositories you pick, their pull requests, and their Pipelines deployments and environments. When you connect, Flamio reads the last 90 days. It also reads
.flamio.ymlon the default branch, and on a pull request that changes it — see Keep the rules in your repository. - Writes: a webhook named "Flamio Delivery", so updates are instant — one for the whole workspace when you are a workspace admin, else one on each repository you are an admin of. With Show Scout results in Bitbucket on, a build status and a report on each commit a Scout check ran on, and a "Flamio config" report on each commit and pull request that changes
.flamio.yml. Flamio never writes to your code. - On the Bitbucket consent screen you allow Flamio to read your account, repositories, pull requests and pipelines, and to manage webhooks.
Connect your workspace
Open Code hosting
Click Settings at the bottom of the sidebar, then Integrations. The Bitbucket tile is under Code hosting. Click Connect.
Sign in to Bitbucket
The first time, click Sign in to Bitbucket and allow Flamio in the window that opens.
Choose a workspace
Under Choose a workspace, click the workspace. Admin marks the workspaces you are an admin of.
Choose repositories
Under Choose repositories, select the repositories this project ships. Enter a name in Search repositories to find one. A repository marked Connected is already on this project; picked again by one of its admins, it gets instant updates. Click Connect — the button names how many you picked. You can connect up to 50 at a time — connect them, then click Add repositories on the tile for more.
Add environment addresses
Under Environments, optionally enter the address each environment runs at — Bitbucket deploys carry none. A repository marked "Updates every 10 min — you're not an admin of this repository" gets instant updates once one of its admins connects it.
Choose whether to show results in Bitbucket
Leave Show Scout results in Bitbucket selected to put each check on its commit, and click Done.
Result
The tile shows Connected as with your Bitbucket name, the Workspace, and each repository with how it updates: Instant updates, Updates every 10 min, or Reading the last 90 days… while the first read runs. Delivery then shows their pull requests and deploys — see Follow your changes on Delivery.
Give an environment its address
Bitbucket deploys carry no site address. To add or change one later:
Open the environment
Click Delivery in the sidebar, then the environment's card.
Enter the address
In the panel, click Add address — or Edit address beside the one it has. Enter the full address, starting with https:// or http://, and click Save. Remove clears it.
The panel then opens the environment at that address. An address you entered stays until you change it. Editing it needs the Editor, Admin or Owner role.
Show Scout results in Bitbucket
With Show Scout results in Bitbucket on, each Scout check your pipeline runs, and each staging check, shows on its commit in two places:
- A build status named "Flamio Scout" — in progress while a pipeline's check runs, then passed or failed; a staging check shows once it ends. When the commit is the head of a pull request's source branch, the status shows on the pull request.
- A "Flamio Scout" report — the verdict, the findings by severity, and a link to the run in Flamio.
The setting covers every project connected to the workspace. Turning it off stops new results; results already on commits stay.
Block a merge when a check fails
A failed check blocks a merge only where the workspace requires passing builds. In Bitbucket, add a branch restriction on the target branch with Minimum number of successful builds for the last commit with no failed builds and no in progress builds. On the Premium plan, also turn on Prevent a merge with unresolved merge checks — on other plans Bitbucket warns but lets the merge through.
With Block merges on, a check whose findings block the merge fails its build status too, and its summary starts with Merge blocked and the reason — see How Flamio runs your delivery.
Reconnect, unlink or disconnect
- Bitbucket access was removed on the tile or on Delivery means Flamio can no longer read Bitbucket. Click Reconnect and allow Flamio again. The board keeps what it has meanwhile.
- Unlink from this project (the icon beside a repository) stops this project getting the repository's pull requests and deploys. History already on Delivery stays.
- Disconnect stops Bitbucket for every project of your organization and deletes Flamio's webhooks. If Flamio could not delete some, the message names how many "Flamio Delivery" webhooks to delete in Bitbucket.
- Disconnect does not withdraw the access you allowed. To withdraw it, revoke Flamio in your Bitbucket personal settings, where Bitbucket lists the apps you authorized.
Limitations
- Flamio connects Bitbucket Cloud only — not Bitbucket Data Center or Server. For GitHub, see Connect GitHub. For the others, your pipeline reports its checks and deploys with a CI key — see Report your deploys.