Bitbucket
Pull requests, merges and pushes. Ticket progress and the deploy gate work like they do with GitHub.
Early access
This connector is new. Some parts are still coming (listed below). If you can't connect it yet, ask us to switch it on.
What SeamTrail reads
- Pull requests: when they are opened and merged.
- Pushes.
- Ticket numbers in branch names, titles and descriptions. They link a pull request to its tickets.
So ticket progress (merged to dev, on stage, in prod) and the deploy gate work for Bitbucket, like for GitHub.
How changes arrive
- Webhook, set on each repository. It sends pushes, and pull requests when they are created and merged.
- During early access, we set up this webhook together with you. Automatic setup is coming soon.
Permissions
| Permission | Why SeamTrail asks for it |
|---|---|
| Account: read | Know which workspace you connected. |
| Repositories: read | Read your repositories. |
| Pull requests: read | Read pull requests. |
| Webhooks: read and write | Kept for setting up webhooks for you (coming soon). |
Connect
- Open your org's Settings → Tools.
- Next to Bitbucket, click Connect. (Org Admins and Managers.)
- Approve SeamTrail in Bitbucket.
- Set up the repository webhooks (see above).
SeamTrail connects the first workspace of the Bitbucket account that approves. Connect with an account whose first workspace is the one you mean.
Linking a Bitbucket repo to a feature needs an org Admin or Manager.
Coming soon
- Reading pull request comments.
- Setting up the repository webhooks for you.