Bitbucket
Bitbucket Pipe
Bitbucket Pipe adds a comment with a summary of a run to a Pull Request:
This summary will contain:
- Status of a test run
- Number of failed/passed/skipped tests
- Stack traces of failing tests (first 10)
- Screenshots of failed tests (if available)
- List of 5 slowest tests
🔌 Тo enable Bitbucket pipe set BITBUCKET_ACCESS_TOKEN in Bitbucket Repository variables
To use the BITBUCKET_ACCESS_TOKEN from Repository Access Tokens in Bitbucket Pipelines, follow these steps:
- In Bitbucket, go to your repository settings.
- Select “Repository Access Tokens” under the “Access management” section.
- Create a new Access Token, granting it the necessary permissions (e.g., read and write for the repository).
Now, you need to add this token as an environment variable in Bitbucket Pipelines:
- Go to “Pipelines” in your repository settings.
- Select “Repository variables” under the “Settings” section.
- Add a new variable with the name BITBUCKET_ACCESS_TOKEN and paste the token
Once you’ve done that, your pipelines.yml configuration file will automatically use this token. Here’s how it should look:
Keep Outdated Reports
If a pipeline is executed multiple times, comment with previous reports will be deleted. To keep them pass BITBUCKET_KEEP_OUTDATED_REPORTS
variable: