Gitlab is an application to code, test, and deploy code collaboratively. It provides Git repository management, code reviews, issue tracking, activity feeds, wikis, and continuous integration features.
Integrating Blackfire with Gitlab enables you to automate the performance testing of your code any time you modify it.
The following options require that Backfire is able to reach the HTTP server serving the Merge Request version of the code.
The expected workflow is as follows:
The first step to configure Blackfire in the above mentioned workflow is to create a webhook payload, that Gitlab will use to let Blackfire run the test scenarios.
Please read the builds API documentation to configure them.
In order to make sure that Gitlab 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|
external_id makes it possible for Blackfire to point the build report
notification to the correct commit. The
external_parent_id makes it
possible for you to write comparison assertions.
Blackfire’s PHP SDK enables to test the performance of your code without deploying it. You will need to configure it to:
Anytime a build report is available, the Gitlab notification channel updates the commit status on the corresponding Merge Request.
You must make sure to create the webhook payload like described above.
To configure a Gitlab notification channel, open the dashboard build tab of the
related Blackfire environment and look for the Notification Channels section.
Add a new notification channel. The configuration requires the repository
https://gitlab.example.com/api/v4/projects/17) and a Gitlab
Token to be able to post build statuses on Merge Requests.