CircleCI#

Lets assume a basic CircleCI configuration file, .circleci/config.yml:

jobs:
  build_and_test:

    steps:
      - checkout
      - run:
          name: Run tests
          command: python -m pytest

To add BlueRacer support, add another run step, so the configuration file looks like so:

jobs:
  build_and_test:

    steps:
      - checkout
      - run:
          name: Run tests
          command: python -m pytest
      - run:
          name: Upload test report to BlueRacer.io
          command: |
            bash <(curl -s https://app.blueracer.io/upload)

That’s it, you’re done!

Missing Pull Request ID#

By default, CircleCI automatically runs your workflows for every commit in every branch. As such, a run for a Pull Request will start before your Pull Request is even created. How so?

The process to create a Pull Request consists of these steps:

Create a new commit in a local branch.
Push the local branch to a new branch on GitHub.
Create a Pull Request from this new branch to your main branch.

CircleCI will start running already at step 2.! At this stage, the Pull Request does not yet exist! So when the test report is uploaded to BlueRacer, it doesn’t know the Pull Request ID and hence BlueRacer does not know which Pull Request to post a comment to.

There are three possible solutions to this problem: