Bitbucket Cascade Merge is a service used to automatically cascade changes after a pull request has been successfully merged (fulfilled). This feature has not been ported to Bitbucket Cloud.
More information can be found on the Bitbucket Server automatic branch merging documentation. Besides semantic version that is currently not supported, the behaviour tries to be the same.
You can show you interest and vote for this feature : BCLOUD-14286
- A service to host this service (eg. Amazon ECS)
- An account on bitbucket.org with r/w privileges to the project
The application password will be used to call the Bitbucket API and fetch/push the repository.
- Open https://bitbucket.org/account/user/{{username}}
- Go to Access Management > App passwords
- Click on Create an app password
- Type a label and select the following permissions :
- Repositories : Read, Write
- Pull Requests : Read, Write
- Copy the password somewhere safe, you will need it later to configure environment variables
- Navigate to the repository you want to activate cascade merges
- Go to Settings > Workflow > Webhooks
- Click on Add webhook
- Type a title, the url of your container and select Choose from a full list of triggers : Pull Request > Merged
Security notice: you can use a token query parameter in the url field
(eg. ?token=your-random-token) that needs to match the configured value
of the TOKEN environment variable.
The container can be configured with environment variable.
| Key | Default Value | Description |
|---|---|---|
| PORT | 5000 | Server will listen on this port |
| BITBUCKET_USERNAME | Bitbucket username | |
| BITBUCKET_PASSWORD | Bitbucket app password | |
| TOKEN | Security token |
Was initially created by Samuel Contesse.
docker run \
-e BITBUCKET_USERNAME=<fillme> -e BITBUCKET_PASSWORD=<fillme> -e TOKEN=<fillme> \
--publish 5000:5000 \
--name bcm \
morpheancloud/bitbucket-cascade-merge
Libgit2 v1.5.1 must be installed if you do not use the Docker image provided.