Bitbucket is an Atlassian git product to code, manage and collaborate. It provides Git repository management, code reviews, issue tracking, activity feeds, wikis, and continuous integration features.
Integrating Blackfire with Bitbucket will enable you to automate the performance testing of your code any time you modify it.
Note that in order to do so, you must make sure that any Bitbucket Pull Request can be deployed. Blackfire’s tests can only be run on a deployed environment.
The expected workflow is as follows:
Please note that only Bitbucket Cloud is supported.
Blackfire.io is using the API v2 of Bitbucket for commit statuses and as of this writing, Bitbucket Server only supports the v1 API version.
As an alternative method, we recommend you to use the webhooks and write a small script triggering a commit status using the v1 API (which uses your personal credentials).
The first step to configure Blackfire in the above mentioned workflow is to create a webhook payload, that Bitbucket will use to let Blackfire run the test scenarios.
Please read the builds webhook documentation to configure them.
In order to make sure that Bitbucket can receive a notification back from Blackfire, please make sure to configure the following parameters:
||(Mandatory) The endpoint to profile|
||(Optional) Can for instance be the Merge Request reference or title|
||(Mandatory) The Git commit sha1 related to the build|
||(Optional) The unique identifier of the parent build|
The external_id will make it possible for Blackfire to point the build report notification to the correct commit. The external_parent_id will make it possible for you to write comparison assertions.
Anytime a build report is available, the Bitbucket notification channel will update the commit status on the corresponding Merge Request.
You must make sure to create the webhook payload like described above.
To configure a Bitbucket notification channel:
Buildtab of the related Blackfire environment and look for the Notification Channel section.
username/project-name), your Bitbucket username and the Bitbucket app password you have just created to be able to post build statuses on merge requests.