Easily connect your CircleCI jobs to BuildPulse to help you identify and eliminate flaky tests.
See this orb's listing in CircleCI's Orbs Registry for details on usage, or see the example below.
In this example config.yml
snippet, the buildpulse/setup
command installs the BuildPulse uploader and identifies the environment variables that contain the required BuildPulse secrets (Access Key ID and Secret Access Key). Then, after your tests run, the buildpulse/upload
command sends the test results to BuildPulse for analysis.
version: 2.1
orbs:
buildpulse: workshop64/[email protected]
jobs:
build:
docker:
- image: circleci/<some-docker-image>
steps:
- checkout
- run: echo "Run your tests and generate XML reports for your test results"
- buildpulse/upload:
path: test/reports
account-id: <buildpulse-account-id>
repository-id: <buildpulse-repository-id>
workflows:
version: 2
commit:
jobs:
- build